Open jasongrout opened 3 years ago
If I had to guess, based on me doing something similar many times, perhaps 4.0.16-alpha.0 was released by lerna, never committed, and lerna automatically set the latest
dist-tag to this pre-release. If that is what happened, you can mitigate the dist-tag setting by using the lerna publish --pre-dist-tag next
option, which overrides dist-tag
for prereleases: https://github.com/lerna/lerna/tree/main/commands/publish#--pre-dist-tag-tag
This way you always keep latest
to be the latest stable release.
FYI, I am looking at this because we upgraded to react 17, but @nteract/transform-vdom
still has a peer dependency on react ^16. React 17 seems like a very safe upgrade, though.
Oof! This looks like a fallout from the work we've been doing to move packages out of the monorepo over at nteract/nteract and into their own repos.
To me, it looks like the latest tag was accidentally set to 4.0.16-alpha.0, and perhaps that prerelease was accidentally published? If this is true, I'd suggest resetting the npmjs.com latest tag with
Yeah, I'll give this a try.
I'm trying to figure out the latest version of
@nteract/transform-vdom
(which we depend on in JupyterLab).I notice that on npm:
latest
release on npm, which means it is the default version installed when doingnpm install @nteract/transform-vdom
When I compare the actual tarballs on npmjs.com, I see these differences:
In particular, notice there is no change in the actual js files published, and the only change in the package.json is:
To me, it looks like the
latest
tag was accidentally set to 4.0.16-alpha.0, and perhaps that prerelease was accidentally published? If this is true, I'd suggest resetting the npmjs.comlatest
tag with: