asdf-nodejs
asdf-nodejs copied to clipboard
asdf-vm
Node.js plugin for asdf version manager
Node already resolves the correct prefix based on the binary location, the problem with overriding it is that the prefix can be customized to a different location in the .npmrc...
Plugin nodejs's list-all callback script failed with output: env: bash\r: No such file or directory
After running asdf list all nodejs I get the following error ``` Plugin nodejs's list-all callback script failed with output: env: bash\r: No such file or directory ``` Any help...
asdf plugins should clearly list their dependencies required for the plugin to operate as expected. The core repo has had issues opened on this matter, most recently https://github.com/asdf-vm/asdf/issues/1176 Because of...
Today I upgraded from Node 6.7 to 6.8, and now my global NPM installations all say something like: ``` No such command in 6.8.0 of nodejs ``` There's no reason...
 commit aded55ba was the last one to allow installing lts versions. commit 5d34772d and after show many hundred lines of output regarding unbound variable access before giving "node-build: definition...
Using asdf-nodejs (from master) on macOS, I'm seeing a problem with global packages starting in node 16. This works fine: ``` asdf plugin install nodejs asdf install nodejs 14.19.3 asdf...
When you run `asdf local nodejs lts` it writes `nodejs lts` to `.tool-versions`. It should probably write what it resolves to instead, ie `nodejs 16.15.1` or better yet, probably `nodejs...
When using nvm, a valid `.nvmrc` file is ``` 14 ``` Which means default to the latest node 14 release. Docs here: https://github.com/nvm-sh/nvm#nvmrc However, when using asdf-nodejs with this `.nvmrc`...
It would be nice if we could support the `musl` build (https://github.com/nodejs/unofficial-builds#builds)
When this plugin is installing packages from `.default-npm-packages`, it uses the `-g` flag. However, in new versions of npm, this gives a deprecation warning: ``` npm WARN config global `--global`,...
