You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@LeaVerou Hey, sorry for not answering that before! I missed this issue somehow.
I don't know where those weird versions come from. They are dated at the time of the creation of the NPM package... so I guess they may have been mistakes, or automatically created maybe?
Anyway, I'm pretty sure they are safe to remove.
Activity
LeaVerou commentedon Nov 23, 2015
@Golmote any ideas where the 9000 came from? Is it safe to remove?
Golmote commentedon Jul 5, 2016
@LeaVerou Hey, sorry for not answering that before! I missed this issue somehow.
I don't know where those weird versions come from. They are dated at the time of the creation of the NPM package... so I guess they may have been mistakes, or automatically created maybe?
Anyway, I'm pretty sure they are safe to remove.
mAAdhaTTah commentedon May 27, 2018
@Golmote I still see
'9000.0.1'innpm view prismjs. Can we unpub that too?Golmote commentedon May 27, 2018
I do not have access to our npm repo. Only @LeaVerou can do this at the moment.
nezhar commentedon Oct 10, 2019
Removing this would be great as it will help to keep a consistent versioning.
Currently this is causing also confusion in services such as https://stackblitz.com/.
Updating to the latest version of the dependencies causes it to take
9000.0.1Can be tested here: https://stackblitz.com/edit/ngx-documentary
mAAdhaTTah commentedon Oct 16, 2019
I may be able to handle this now. Let me look at it this evening.
mAAdhaTTah commentedon Oct 18, 2019
Seems to have worked? Although I still see the version here: https://www.npmjs.com/package/prismjs
Dunno if that's a caching thing; will recheck in a bit.
mAAdhaTTah commentedon Oct 18, 2019
Doesn't seem to be going–sent in a support ticket. Will update here with latest.
mAAdhaTTah commentedon Oct 21, 2019
This is being handled by npm support and should be fixed shortly.
joskuijpers commentedon Jul 12, 2022
The versions still show up for me, and they trigger an automated 'dependency check' of Renovate Bot continuously.
Can this be looked at again?
RunDevelopment commentedon Jul 12, 2022
@joskuijpers They are no longer listed.
npm view prismjs versionsMy guess is that Renovate uses an internal database, and that this database is outdated. You might want to report this bug.
joskuijpers commentedon Jul 12, 2022
Ah I found the trouble.... I am not actually using NPM but a CDN:
https://cdnjs.com/libraries/prism still knows of version 9000
RunDevelopment commentedon Jul 12, 2022
I've asked them if it's possible to remove the v9000.0.1 (cdnjs/cdnjs#14145). Let's see how this goes.