Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to install prepacked tarbal globally with volta #465

Closed
stefanpenner opened this issue Jun 6, 2019 · 2 comments
Closed

Unable to install prepacked tarbal globally with volta #465

stefanpenner opened this issue Jun 6, 2019 · 2 comments

Comments

@stefanpenner
Copy link
Contributor

stefanpenner commented Jun 6, 2019

During ember-cli's release process, we run an npm pack and then try to install the result of that locally. Volta intercepts this, and the command fails with:

ember-cli-3.11.0-beta.2.tgz
up to date in 0.035s
Volta error: Global package installs are not supported.

Use `volta install ./ember-cli-3.11.0-beta.2.tgz` to add a package to your toolchain (see `volta help install` for more info).

Unfortunately, following the instructions also fails:

 s/e/ember-cli ╍ {beta}+ volta install ./ember-cli-3.11.0-beta.2.tgz                                                                                                                                                                                                                   (14s 482ms)
error: Could not parse tool spec `./ember-cli-3.11.0-beta.2.tgz`

Please supply a spec in the format `<tool name>[@<version>]`.
@charlespierce
Copy link
Contributor

Thanks for the report @stefanpenner We’ve got an issue tracking being able to install a tarball #427

If the goal is just to globally install and make sure the install process works (but not to run it), then you can use VOLTA_UNSAFE_GLOBAL=1 as an environment variable to disable the global intercept. Unfortunately, because of how the files are laid out in Volta, while this will allow npm i -g to run, the resulting binaries don’t end up on your PATH, so running the command afterwards doesn’t work.

@stefanpenner
Copy link
Contributor Author

@charlespierce oops, i didn't see that one!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants