-
Notifications
You must be signed in to change notification settings - Fork 102
Unable to use Kraken #27
Comments
Have you tried with node 4 or node 6? We haven't tested this on node 8 yet so that might be the issue |
Oh, okay. Do I have to downgrade from Node 8 to Node 4 for this or is these any other way around it ? |
as mentioned above, try node 6.. I'll take it as an action item to try with node 8. |
Also won't run with node 7.2.1 --- well it did run with node v 7.2.1 using this command node index.js instead of the one suggested on the documentation. :) |
works with node v8/npm v5. Need more info about the failure for you. Can you provide OS version as well? In general, we are probably going to move away from this react pattern (anemone) in favor of what we use internally. |
So, I wanted to see how Kraken works out and tried running the same. I followed all the instructions yet was unable. The error is show below. I couldn't figure out the error/warning shown below. If someone could explain how to get Kraken working I'd be glad. Thanks in advance
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]
prestart: [email protected]prestart: no script for prestart, continuing6 silly lifecycle [email protected]
7 info lifecycle [email protected]
start: [email protected]start: unsafe-perm in lifecycle true8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/abhinavralhan/kraken-example-with-shoppingcart/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/gamesstart: CWD: /home/abhinavralhan/kraken-example-with-shoppingcart10 verbose lifecycle [email protected]
11 silly lifecycle [email protected]
start: Args: [ '-c', 'grunt build && node index.js' ]start: Failed to exec start script12 info lifecycle [email protected]
13 verbose stack Error: [email protected] start:
grunt build && node index.js
13 verbose stack spawn ENOENT
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:33:16)
13 verbose stack at emitTwo (events.js:125:13)
13 verbose stack at ChildProcess.emit (events.js:213:7)
13 verbose stack at maybeClose (internal/child_process.js:887:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:208:5)
14 verbose pkgid [email protected]
15 verbose cwd /home/abhinavralhan/kraken-example-with-shoppingcart
16 verbose Linux 3.19.0-84-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v8.0.0
19 verbose npm v5.0.3
20 error file sh
21 error code ELIFECYCLE
22 error errno ENOENT
23 error syscall spawn
24 error [email protected] start:
grunt build && node index.js
24 error spawn ENOENT
25 error Failed at the [email protected] start script.
25 error This is probably not a problem with npm. There is likely additional logging output above.
26 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: