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
diligent doesn't work with NPM scoped packages (eg. @angular/cli).
This is because 44419b8 changed the NPM registry URL from https://registry.npmjs.org/{package}/{version} to https://registry.npmjs.org/{package}?version={version}, which for some weird reason doesn't support scoped packages, even if the slash (/) is URL encoded as %2F.
I've sent an email to NPM support about this behavior, but its unlikely that they will address it anytime soon.
To revert back to using https://registry.npmjs.org/{package}/{version}, we need to strip any symbols before the version, as https://registry.npmjs.org/{package}/{version} only supports exact versions, unlike https://registry.npmjs.org/{package}?version={version}.
The text was updated successfully, but these errors were encountered:
As you may have found out already, the version query string parameter is no longer supported in our package APIs.
Even your https://registry.npmjs.org/base-64?version=%5E0.1.0 example just returns a list of all versions (same as https://registry.npmjs.org/base-64).
Therefore we shouldn't use https://registry.npmjs.org/{package}?version={version} anymore.
diligent
doesn't work with NPM scoped packages (eg.@angular/cli
).This is because 44419b8 changed the NPM registry URL from
https://registry.npmjs.org/{package}/{version}
tohttps://registry.npmjs.org/{package}?version={version}
, which for some weird reason doesn't support scoped packages, even if the slash (/
) is URL encoded as%2F
.I've sent an email to NPM support about this behavior, but its unlikely that they will address it anytime soon.
To revert back to using
https://registry.npmjs.org/{package}/{version}
, we need to strip any symbols before the version, ashttps://registry.npmjs.org/{package}/{version}
only supports exact versions, unlikehttps://registry.npmjs.org/{package}?version={version}
.The text was updated successfully, but these errors were encountered: