Issue during NPM install

[esri]

Issue during NPM install

[nikolaswise]

@jhough10 I can't repro this, but I have a hunch on what might be causing it. I'm assuming your in the internal network? Try setting up your SSH keys so you terminal can chat with git - both press and press-kss are tools we developed in-house for this project and are being installed from Github rather than from NPM. This will help: https://help.github.com/articles/generating-ssh-keys

If that doesn't do it, this weekend we can get those tools on NPM, but I think the SSH keys should do it.

[nikolaswise]

@jhough10 Pull down from upstream and try again before going down the SSH road - we think the git// protocol might have been exploding, so we switched to https.

[paulcpederson]

@jhough10 if this doesn't work you can always just clone those two repos into your node_modules folder as a quick work around:

cd node_modules/
git clone https://github.com/patrickarlt/press.git
git clone https://github.com/paulcpederson/press-kss.git
cd ../

But that should be a last resort if we just can't get npm install working.

[jhough10]

Added the upstream, pulled the latest and noticed the HTTPS change for the repo. Worked like a champ, but during the npm install it died on grunt prepublish.

npm ERR! [email protected] prepublish: `grunt prepublish`
npm ERR! Exit status 6
npm ERR! 
npm ERR! Failed at the [email protected] prepublish script.
npm ERR! This is most likely a problem with the calcite-web package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt prepublish
npm ERR! You can get their info via:
npm ERR!     npm owner ls calcite-web
npm ERR! There is likely additional logging output above.
npm ERR! System Darwin 13.3.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/just0001/Sites/Esri-Calcite
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code ELIFECYCLE
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/just0001/Sites/Esri-Calcite/npm-debug.log
npm ERR! not ok code 0

[nikolaswise]

@jhough10 I had this problem when attempting to repro your original issue on the internal network. I'll connect with @kpettijohn and see if he has any thoughts.

[paulcpederson]

@jhough10 do you have grunt installed globally?

npm install -g grunt-cli

This error means that on the "prepublish" step for our module (calcite-web) it is failing. The prepublish step basically has grunt run a couple tasks to get the repo ready for development. My guess is that it is trying to run grunt prepublish and can't because something is wrong with grunt, or you just don't have it?

[jhough10]

Wow. This is getting more fun with every step, I personally don't think I have ever seen this many errors with grunt or npm before.

I opted to create a new SSH key with Github and have that authenticated. I figured I would clear the node_modules folder and start from scratch just in case. After running $ npm install and only seem to get this warning npm WARN cannot run in wd [email protected] grunt prepublish (wd=/Users/just0001/Sites/Esri-Calcite). Not a big deal so I moved on.

However, now I get this error when running $ grunt

jhough:Esri-Calcite just0001$ grunt
Running "connect:server" (connect) task
Started connect web server on http://0.0.0.0:8888

Running "shell:build" (shell) task
build
building page index.html
pressed in: 34ms

Running "newer:imagemin:doc" (newer) task
No newer files to process.

Running "concat:doc" (concat) task
File docs/source/assets/js/libs/calcite-web.js created.

Running "sass:doc" (sass) task
OptionParser::NeedlessArgument: needless argument: --sourcemap=none
  Use --trace for backtrace.
Warning: Exited with error code 1 Use --force to continue.

Aborted due to warnings.

[paulcpederson]

@jhough what's strange isn't the errors, it's that you're the only one!

What I will tell you is that at least the two errors you have now are actually the same error. It can't run prepublish because part of running prepublish is running sass which is somehow broken because your sass can't seem to figure out how to ignore an option that is actually needed and calls it needless...

I think this could actually be a system sass thing. What do you get when you run sass -v ?
You need at least Sass 3.4.0, so if you're rocking something under that you should try to update. I think that's something like gem update sass

[jhough10]

@paulcpederson I have Sass 3.4.3 (Selective Steve) installed. So i just uninstalled sass and compass, then clean installed them and it seemed to work fine. Guess my gems where corrupted along the way. Thanks for your assistance on this.

[nikolaswise]

@jhough10 Another case of the Mystery Weird Gem Thing. Glad it worked out!

[paulcpederson]

Yay!!