summaryrefslogtreecommitdiff
path: root/bin/spack.bat
diff options
context:
space:
mode:
authorTodd Gamblin <tgamblin@llnl.gov>2023-01-18 14:18:33 -0600
committerGitHub <noreply@github.com>2023-01-18 14:18:33 -0600
commitc9e85ada1542862a2c2919c2c30b63e9d43a0fe9 (patch)
tree2ec8957a0d59c7fd415c48ebbc07e9a2a714b7e7 /bin/spack.bat
parent8eb803ab4cf663f4d4036b51a0451d63d40ca7e5 (diff)
downloadspack-c9e85ada1542862a2c2919c2c30b63e9d43a0fe9.tar.gz
spack-c9e85ada1542862a2c2919c2c30b63e9d43a0fe9.tar.bz2
spack-c9e85ada1542862a2c2919c2c30b63e9d43a0fe9.tar.xz
spack-c9e85ada1542862a2c2919c2c30b63e9d43a0fe9.zip
npm: Add latest version, update build (#34947)
* npm: Add latest version, update build The `npm` package had gotten a bit long in the tooth and only suported the last version for which running `configure` / `make` / `make install` actually worked. - [x] Update the package to support npm@9, in which `npm install .` works properly and installation is easier. - [x] Update the package so that `npm@6:8` also install successfullly. The incantation that is *supposed* to work on these versions is `node bin/npm-cli.js install $(node bin/npm-cli.js pack . | tail -1)`, but depending on the version one of `npm install` or `npm pack` will fail when run straight from the install directory. So now we just manually copies things over. This seems to make the `npm` install much more reliable for all of `npm@6:9` (at least for me). udpates the `npm` build to support versions 6-9 and fixes the install for all of them on macos. * update for review
Diffstat (limited to 'bin/spack.bat')
0 files changed, 0 insertions, 0 deletions