It looks like updating NPM when making a release stable does not yet work, even though we looked into this before. I made version 2.4.456 stable today, but NPM still shows version 2.3.200. What did work is updating the next tag for pre-release 2.5.207, so it looks like the release script doesn't handle release updates correctly in contrast to release creations which work.
Please find the cause of this, and for now update the latest tag on NPM to version 2.4.456 manually.
timvandermeij
All 7 comments
Updated the tag.
brendandahl
on 1 Jun 2020
Hm, I'm not sure if it worked correctly. It has been updated, but it seems that the v prefix should not be there. Contrary to the GitHub tags, the NPM tags only consist of the version number. Visiting https://www.npmjs.com/package/pdfjs-dist/v/v2.4.456 also results in a not-so-gracefully handled React error on NPM, which is also surprising.
Could you re-push the latest tag with just 2.4.456 as version?
timvandermeij
on 1 Jun 2020
I am also getting an npm error as of this morning.
JessWallin
on 1 Jun 2020
Yes, NPM seems to have some problems with the tag name. Fortunately https://www.npmjs.com/package/pdfjs-dist/v/2.4.456 already exists, we just need to re-push the latest tag to fix this.
timvandermeij
on 1 Jun 2020
There seems to be some issues with the latest tag and npm. Might be related to this issue.
https://www.npmjs.com/package/pdfjs-dist won't even load; Service Unavailable.
trs
on 2 Jun 2020
I update npm again. Thought I used the same command as before but I guess not.
brendandahl
on 2 Jun 2020
This works now. Thanks!
timvandermeij
on 2 Jun 2020
Related issues
aaronshaf
路
3Comments
kleins05
路
3Comments
liuzhen2008
路
4Comments
anggikolo11
路
3Comments
zerr0s
路
3Comments
Most helpful comment
I update npm again. Thought I used the same command as before but I guess not.