JS engines that support local installed node should prefer local installed npm #92
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of using webjars npm.
The latest available (classic) webjars npm is totally outdated and can't be used with node 13+ (current node version is 20).
Related:
I like the idea suggested in #70 to just use the system installed npm if using a local installed js engine that supports node. Usually when installing node npm comes along, so that should work, also it's much more future proof, because usually the npm version installed locally is compatible with the local node installation (most people will use a node version manager like nvm anyway which handles that).
Fixes #70
Fixes #51
Fixes #82
Fixes typesafehub/npm#28