-
Notifications
You must be signed in to change notification settings - Fork 143
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
bug: nodejs plugin segfault with node 11.1.0
#368
Comments
I notice the |
Unfortunately, yes. I updated to v0.13.1, removed the nodejs plugin, reinstalled it, installed the latest node version in my homedir, set it as global and local default and then went to the old project's directory, installed nodejs 11.1.0 and still when I try to run |
@RSeidelsohn with such an old version of Node.js, I wouldn't be surprised if this was an issue with the plugin itself and how it handles installing such an old version. I suggest raising the issue in the plugin repo and seeing what help you can get there as this is not clear it is an issue in the core tool. Edit: I'm unsure if the author is able to "transfer issues" to other Repos, but I can perform this action if you would like to keep the context and participants? |
That would be great, thank you! I can not do this or at least do not find any option to do so. |
Describe the Bug
When installing
nodejs 11.1.0
with asdf,npm
always results in a segmentation fault - no matter what 11-ish version of nodejs I try.Unfortunately,
nodejs 11.1.0
is the latest version I can use for that project, as it depends on old tools that fail with later versions. Since nodejs is only used locally, it's not a security issue.Steps to Reproduce
asdf install nodejs 11.1.0
asdf local nodejs 11.1.0
npm
segmentation fault (core dumped) npm
Expected Behaviour
npm should run and output it's usage information. nvm for example installs
npm 6.4.1
alongside withnodejs 11.1.0
and that runs fine. I would expect the same behaviour with asdf.Actual Behaviour
segmentation fault (core dumped) npm
Environment (old)
Environment (after I updated asdf)
asdf plugins affected (if relevant)
nodejs
The text was updated successfully, but these errors were encountered: