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
Is your feature request related to a problem? Please describe.
Some projects have dependencies that are not part of the npm registry and are not hosted on GitHub, but instead are specified using the git+http(s) scheme. An example would be https://gitlab.com/openengiadina/geopub/-/blob/v0.2.0/package-lock.json#L769
It's currently not possible to use npmlock2nix with these lockfiles.
Describe the solution you'd like
Support git+http(s) urls for specifying versions.
Describe alternatives you've considered
both not very practical:
Mirror the dependency on GitHub
upload the dependency on npm
The text was updated successfully, but these errors were encountered:
I think we are hallf way there with #88 being merged. We will have to write a bit more elaborate URL parsing/handling code. In this case we probably want to use git with the HTTPS protocol as seen in the URI. This means the URL check has to become smarter and we will have different flavors of it.
The makeGithubSource function has to be generalized into handling generic git+http(s) URLs while keeping the GitHub specific code for that special GitHub syntax.
Does NPM have a gitlab: prefix for GitLab sources just as they have one for GitHub?
Is your feature request related to a problem? Please describe.
Some projects have dependencies that are not part of the npm registry and are not hosted on GitHub, but instead are specified using the
git+http(s)
scheme. An example would be https://gitlab.com/openengiadina/geopub/-/blob/v0.2.0/package-lock.json#L769It's currently not possible to use npmlock2nix with these lockfiles.
Describe the solution you'd like
Support
git+http(s)
urls for specifying versions.Describe alternatives you've considered
both not very practical:
The text was updated successfully, but these errors were encountered: