Error when npm start

[goldenlimit]

When trying to "npm start" this cedar folder, I get an error from Git Bash:

yue7422@YUEW ~/node_modules/arcgis-cedar
$ npm start

arcgis-cedar@0.8.0 prestart c:\Users\Yue7422\node_modules\arcgis-cedar
npm run clean:docs && npm run copy:deps

arcgis-cedar@0.8.0 clean:docs c:\Users\Yue7422\node_modules\arcgis-cedar
rimraf ./site/build

arcgis-cedar@0.8.0 copy:deps c:\Users\Yue7422\node_modules\arcgis-cedar
copyfiles -f node_modules/d3/.js site/build/js & copyfiles -f node_modules/v
ega/.js site/build/js

arcgis-cedar@0.8.0 start c:\Users\Yue7422\node_modules\arcgis-cedar
watch 'npm run build && karma start && npm run copy:docs' src & grunt

Watching run
Watching build
c:\Users\Yue7422\node_modules\arcgis-cedar\node_modules\watch\main.js:75
if (err) throw err;
^

Error: ENOENT: no such file or directory, stat 'c:\Users\Yue7422\node_modules\ar
cgis-cedar\run'
at Error (native)
Running "assemble:dev" (assemble) task
Warning: Layout file (site\source\layouts\layout.hbs) not found. Use --force to
continue.

Aborted due to warnings.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\Program Files (x86)\nodejs\node.exe" "c:\Program Files (x8
6)\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v4.4.3
npm ERR! npm v2.15.1
npm ERR! code ELIFECYCLE
npm ERR! arcgis-cedar@0.8.0 start: watch 'npm run build && karma start && npm r un copy:docs' src & grunt
npm ERR! Exit status 6
npm ERR!
npm ERR! Failed at the arcgis-cedar@0.8.0 start script 'watch 'npm run build &&
karma start && npm run copy:docs' src & grunt'.
npm ERR! This is most likely a problem with the arcgis-cedar package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! watch 'npm run build && karma start && npm run copy:docs' src & gru
nt
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs arcgis-cedar
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls arcgis-cedar
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! c:\Users\Yue7422\node_modules\arcgis-cedar\npm-debug.log

[jgravois]

Error: ENOENT: no such file or directory, stat 'c:\Users\Yue7422\node_modules\ar
cgis-cedar\run'

check out Esri/esri-leaflet-geocoder#156 for an example of augmenting an npm script so that it is able to run two concurrent tasks on windows.

another option (i think) would be to just use Git Bash bash instead of cmd.

[benstoltz]

Sounds like we could switch the watch statement over to "watch \"npm run build && karma start && npm run copy:docs\" src & grunt" and that may fix it. @goldenlimit try that out and let us know if that works.

[goldenlimit]

@benstoltz @jgravois
I switch to my personal mac and go through all the steps and it looks like work, here is the terminal info I get:

I try to ping this url that mentioned in the command: http://localhost:9876/
However, I get nothing show on browser. What should I do next to see the sample within the folder?

[benstoltz]

@goldenlimit that's actually not the right URL. It should be http://localhost:8082 . The one you listed is the karma server for running tests.

Were you able to try that suggestion I made and did it get you past your original error?

[tomwayson]

@benstoltz I think we'll need to do more than just escape the watch command. We'll need to use an npm package to support parallel tasks in Windows b/c & does not work on Windows. My preference is https://www.npmjs.com/package/concurrently b/c I figure if it's good enough for Angular, it's probably good enough for us.

[goldenlimit]

@benstoltz @tomwayson @jgravois
Thanks all guys notes and efforts. I finally make it works on my office mac. I contact @benstoltz and what I did is actually fork this repo and clone locally on my machine. Then npm start and install. All is working now.

Previously, I directly following our README file to "npm install arcgis-cedar" in terminal and I get this error.
I am not sure what is the best way to install this repo, but at least the "clone repo" locally is safe and sounds.

I will keep trying to see what's going on my PC

[benstoltz]

@goldenlimit let's leave this open because it's something that needs to be resolved and will fall by the wayside otherwise.

@tomwayson gotcha, makes sense.

[tomwayson]

@goldenlimit I'm glad you got it working on your mac, but we need to leave this open in order to enable windows users to develop and contribute.

Re: install instructions, npm install arcgis-cedar is for consuming Cedar in an application, not for developing cedar (which is when you would use npm start). That said, we should probably make the first step of the development instructions to fork or download cedar. @goldenlimit would you be interested in PRing that?

[goldenlimit]

@tomwayson Sorry that I am not quite sure if I am understand your request clearly. Correctly me if I am wrong, do you mean I can go and update the step 1 to download and fork the repo locally and then cd cedar folder etc... ❓

Update from PC side:
I did the same workflow as in mac and the http://localhost:8082 works, the page shows up.
However, all the sample doesn't work and the reason is because the cedar js doesn't generated. (http://localhost:8082/js/)

Versus on mac, we see the "dist" folder contains the cedar.js file:

And I check the "cedar" folder, it turns out that 'dist' folder is not generated (This dist folder is coming from bower/npm, right? I wonder if this is the issue that you mentioned):

We'll need to use an npm package to support parallel tasks in Windows b/c & does not work on Windows. My preference is https://www.npmjs.com/package/concurrently

[tomwayson]

do you mean I can go and update the step 1 to download and fork the repo locally and then cd cedar folder etc...

yes

And thanks for the Windows update.

And I check the "cedar" folder, it turns out that 'dist' folder is not generated (This dist folder is coming from bower/npm, right? I wonder if this is the issue that you mentioned)

Could be, though I'd expect the 'dist' folder to be there (it's generated in the npm "build" script, not downloaded from bower/npm), so could be something else. I'd have to play around with it myself to diagnose it.