Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
PackageVersionMismatchError
See original GitHub issueDescribe the bug I’ve released a new version of my package 2 days ago but BundlePhobia can’t find the new version. It’s currently stuck at 0.6.0 even though 2 more versions were released.
Npm link: https://www.npmjs.com/package/nope-validator GitHub link: https://github.com/bvego/nope-validator
To Reproduce https://bundlephobia.com/result?p=nope-validator
Overriding with: https://bundlephobia.com/result?p=nope-validator@0.7.2 shows a PackageVersionMismatchError that reports that it is still stuck on 0.6.0
Expected behavior It should report the newest package version details (0.7.2) and be able to find it. Maybe I missed something - but NPM shows 0.7.2 and I’ve correctly tagged it as such in GitHub
Awesome project by the way!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This was occurring because of the algolia index we used to resolve package versions – it often lagged official npm registry data. This is should be fixed in the next release (by tomorrow) now that we’ve switched to using the official registry.
I’m having the same issue. Our package has a newer released version that isn’t showing up as registered in bundlephobia. Wondering how frequently the data is fetched for this? Why wouldn’t a newly published version be found? It’s version is shown as published on npm.