Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
support for downloading node or npm binaries from Nexus repository
See original GitHub issuePR #330 was awesome and I know that this feature was discussed in the same thread(pushing NPM and Node binaries to Maven Central and making the plugin to fetch the binaries from the Maven repositories instead of using the NPM or Node download URLs)
Is this still being considered? If you think uploading all versions of node/npm to central will be a pain, could you please provide an optional parameter to configure the download URL, something like
<nodeDownloadURL>http://mynexus.com/my/groupid/node/${version}/node-${version}-${platform}-${architecture}.${extension}</nodeDownloadURL>
and replace the variables at runtime to figure out the actual download URL
This would help in fetching the binaries from a private Nexus repo/or any other kind of repository.
If you are ok with either of the options, I can raise a PR for the same 😄
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
How do you configure the plugin so that yarn pulls dependencies from Nexus? My company has Nexus setup to mirror npm, but I can’t figure out how to configure the plugin so that it configures yarn to pull from the Nexus server.
it would be nice if a direct url could be supported. there are ways in maven to ensure the proper binary is selected.