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
If using github url for package.json (e.g. dependencies: { "package-a": "git+ssh://[email protected]/...." }), above error occurs after execute jsgl --local ..
The reason is package-json does not support git url and the issue is here.
As described above, I understand the unnecessity of fetching package from git url (because the aim of js-green-licenses is also for the open source library's license).
However, for some reasons (e.g. there are no private registries in the organization), it is not possible to remove those git url packages.
So I have 3 proposals.
remove package directed to git url before iterating
if package is allow-listed and is directed to git url, do not fetch from npm registry
I have a problem about
PackageNotFoundError
.If using github url for package.json (e.g.
dependencies: { "package-a": "git+ssh://[email protected]/...." }
), above error occurs after executejsgl --local .
.The reason is package-json does not support git url and the issue is here.
As described above, I understand the unnecessity of fetching package from git url (because the aim of
js-green-licenses
is also for the open source library's license).However, for some reasons (e.g. there are no private registries in the organization), it is not possible to remove those git url packages.
So I have 3 proposals.
At last I have a question.
Do you think which workaround is the best?
The text was updated successfully, but these errors were encountered: