-
Notifications
You must be signed in to change notification settings - Fork 757
"npm test" after a successful "npm install" fails with node v7.0.0 from nvm on Mageia Linux x86-64 v6 #1050
Comments
Thanks. Nice find! Also kudos for using 7 Looks like the devtools-config/feature module can't find the feature-flag module. Feel free to play with path.x methods Also install node 6 with nvm |
@jasonLaster : OK, thanks for the update - I'm going to try with v6.9.1. |
Just a small update that I'm getting a very similar problem with node v6.9.1:
I have not played with the path.x methods yet (whatever those are). |
Hmm. Interesting, it works for me on 6.9. Was thinking of path.resolve. Happy to pair on Monday if your free |
@jasonLaster : I see. I can try it on a VirtualBox VM as well. What do you mean by "pair"? Do you mean "pair program"? |
Yea. I can do a google hangout Monday if you're free. My email is
|
@jasonLaster : OK, I might do it. |
Hi! sorry for the late report, but I am getting a very similar report on a relatively up-to-date Debian Sid/Unstable VBox VM with nvm's node v6.9.1 after doing only "npm install" and "npm test". See:
|
@jasonLaster : hi! I am getting this:
here is the yarn-error.log: this is with /usr/bin/node being v6.9.1 on Mageia v6 x86-64. |
@jasonLaster : |
Thanks @shlomif |
@juliandescottes helped me hunt this down! This issue:
is caused by the debugger's node_modules not properly linking the packages like rm -rf node_modules packages/*/node_modules |
Hi all.
"npm test" after a successful "npm install" fails with node v7.0.0 from nvm on Mageia Linux x86-64 v6. I am getting this output:
Please let me know how I can further help.
The text was updated successfully, but these errors were encountered: