Codex review on #400:
- A package added with a range such as npm:demo@^1.2.0 was compared with
npm's unrestricted latest. With latest at 2.0.0 and the newest matching
release at 1.9.0, check kept offering 2.0.0, which Pi never installs
because it keeps the configured range. Only a package added without a
version follows latest now; one with a range or a tag is left to Pi, as
a pinned one already was.
- The private-registry check read the user .npmrc path only from
NPM_CONFIG_USERCONFIG. npm reads its environment case-insensitively, so
a lowercase npm_config_userconfig pointing at an .npmrc with a private
registry was ignored, and the package name went to npmjs. Both
spellings are read now.
The plugin reference, its translations and the built-in skill say which
packages the check leaves to Pi.