-
Notifications
You must be signed in to change notification settings - Fork 17
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
npm bin
is removed in npm v9
#23
Comments
npm v9 has been released and will be |
I've found the following workaround via (setq add-node-modules-path-command "npm exec --package=npm@8 -- npm bin") |
npm bin
will be removed in npm@9.0.0npm bin
is removed in npm@9.0.0
npm bin
is removed in npm@9.0.0npm bin
is removed in npm v9
Hey! Thanks for sharing. I didn't notice this issue at all, sorry. That is unfortunate that they removed this command. Maybe until we find something people can at least refer to your workaround. |
The following workaround using (setq add-node-modules-path-command "echo \"$(npm root)/.bin\"") EDIT: Though this is still tricky. |
I used to be grateful for the workaround at #23 (comment), but now it seems that I need to set the following I have to configure it as follows. (setq add-node-modules-path-command '("echo \"$(npm root)/.bin\""))) |
I have also been using the workaround @hyakt mentions and that works fine for me on Linux. It didn’t work well on Windows, though (because the default shell is CMD still). It would probably make sense to use some elisp to concatenation in the .bin. |
Hello. I notice the
npm bin
command will be removed in npm@9.0.0 when reading the release note of npm@9.0.0-pre.0.This elisp package heavily depends on
npm bin
, so I worry the package will require some action in the future. Although, I have no good idea right now.I hope this sharing will be of some help.
See also:
npm bin
npm/cli#5459The text was updated successfully, but these errors were encountered: