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 load on NPM 5 #439

Closed
eslachance opened this Issue Jul 5, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@eslachance

eslachance commented Jul 5, 2017

NPM version 5 (released with node 8) has completely changed the way that dependencies function. Unfortunately, c9sdk is now completely nonfunctional in this version. I just learned this the hard way attempting to re-install from scratch because of #438 .

The install itself seems to completely without errors, but attempting to start the server (or run node servers.js --help) will complain about modules not being found. Modules which are probably subdependencies, which are no longer directly useable if not part of the specific package.json that a module uses. So basically, amd-loader and architect are called from the main app but are sub-dependencies of something else, so they need to be reinstalled.

I would have continued to install them however I hit a wall being told Error: Cannot find module 'c9/urls' which I don't know how to go around.

To reproduce this, simply install nodejs version 8.1.3 , then run npm i -g npm to get the latest npm version. Then follow the instructions on how to install c9sdk as usual (git clone, install.sh).

I fully understand that Node 8 is Current and not LTS. However, there's no denying that it's an issue that should be resolved as soon as possible. Right now, I am completely unable to use c9 at all which is a massive bummer.

@nightwing

This comment has been minimized.

Member

nightwing commented Jul 5, 2017

run git checkout HEAD -- node_modules after npm install

@eslachance

This comment has been minimized.

eslachance commented Jul 5, 2017

Hmm. That's interesting. It did function. Perhaps this should be added to the install guide?

@eslachance

This comment has been minimized.

eslachance commented Jul 5, 2017

Resolved with Nightwing's comment (though I'm not sure why)

@eslachance eslachance closed this Jul 5, 2017

@nightwing

This comment has been minimized.

Member

nightwing commented Jul 6, 2017

Sorry i didn't write more detailed explaination yesterday.
The issue happens because npm5 deletes all folders in node_modules that it didn't create, so the dependencies which cloud9 has in git are deleted after npm install.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment