search

raineorshine / npm-check-updates

Find newer versions of package dependencies than what your package.json allows
Other
9.35k stars 323 forks source link

Not working with packages published on Github Packages Registry #1298

Open piranna opened 1 year ago

piranna commented 1 year ago

Steps to Reproduce

Steps:

  1. Publish some packages on Github Packages Registry
  2. Depend on them, using a .npmrc file in the project root
  3. Update them
  4. Run npm-check-updates

Current Behavior

Packages from npmjs are correctly identified for new versions, but it says there's no new packages versions for the ones in Github Packages Registry. I have some of them published in both registries, don't know if that can affect.

Expected Behavior

Use the project .npmrc file pointing to Github Packages Registry, and detect and suggest the new versions of the packages on Github Packages Registry.

piranna commented 1 year ago

Ok, false positive, I didn't have a .npmrc file in that particular repo, sorry 🤦🏻 . After adding it, it worked. I have seen it in another ones, I'll left it open to check if it's the same error on my side or if I can reproduce it.

raineorshine commented 1 year ago

Sure! Let me know if you run into it again.

piranna commented 1 year ago

Sure! Let me know if you run into it again.

Will do :-)