Advertisement
bogdanbiv

imrsk_start_functional

Mar 29th, 2016
165
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.63 KB | None | 0 0
  1. $ npm run dev
  2.  
  3. > [email protected] dev /home/bogdanbiv/Projects/imrsk
  4. > concurrently --kill-others "npm run start-webpack" "npm run start-dev"
  5.  
  6. [0]
  7. [0] > [email protected] start-webpack /home/bogdanbiv/Projects/imrsk
  8. [0] > better-npm-run start-webpack
  9. [0]
  10. [1]
  11. [1] > [email protected] start-dev /home/bogdanbiv/Projects/imrsk
  12. [1] > better-npm-run start-dev
  13. [1]
  14. [1] running better-npm-run in /home/bogdanbiv/Projects/imrsk
  15. [0] running better-npm-run in /home/bogdanbiv/Projects/imrsk
  16. [1] Executing script: start-dev
  17. [1]
  18. [0] Executing script: start-webpack
  19. [0]
  20. [1] to be executed: nodemon --exec ./node_modules/.bin/babel-node -- ./server/server.js
  21. [0] to be executed: ./node_modules/.bin/webpack-dev-server --hot --inline --no-info --colors
  22. [1] [nodemon] 1.9.1
  23. [1] [nodemon] to restart at any time, enter `rs`
  24. [1] [nodemon] watching: *.*
  25. [1] [nodemon] starting `./node_modules/.bin/babel-node ./server/server.js`
  26. [0] babel-relay-plugin-loader: using schema at [/home/bogdanbiv/Projects/imrsk/graphql/schema.json]
  27. [1] babel-relay-plugin-loader: using schema at [/home/bogdanbiv/Projects/imrsk/graphql/schema.json]
  28. [0] http://localhost:8080/
  29. [0] webpack result is served from http://localhost:8080/1.0.4/
  30. [0] content is served from /home/bogdanbiv/Projects/imrsk
  31. [1] info: Starting application npm_package_name=isomorphic-material-relay-starter-kit, npm_package_version=1.0.4, NODE_ENV=development, HOST=127.0.0.1, PORT=4444, PUBLIC_URL=undefined, process_title=/usr/local/bin/node, process_pid=3727, objectPersistence=cassandra, CASSANDRA_KEYSPACE=imrsk, CASSANDRA_CONNECTION_POINTS=localhost
  32. [0] /home/bogdanbiv/Projects/imrsk/node_modules/sockjs/lib/trans-websocket.js:157
  33. [0] return this.session.close(3000, 'No response from heartbeat');
  34. [0] ^
  35. [0]
  36. [0] TypeError: Cannot read property 'close' of null
  37. [0] at WebSocketReceiver.heartbeat_timeout (/home/bogdanbiv/Projects/imrsk/node_modules/sockjs/lib/trans-websocket.js:157:26)
  38. [0] at [object Object]._onTimeout (/home/bogdanbiv/Projects/imrsk/node_modules/sockjs/lib/trans-websocket.js:75:24)
  39. [0] at Timer.listOnTimeout (timers.js:92:15)
  40. [0]
  41. [0] npm
  42. [0] ERR! Linux 4.2.0-34-generic
  43. [0] npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start-webpack"
  44. [0] npm ERR! node v5.8.0
  45. [0] npm ERR! npm v3.7.3
  46. [0] npm ERR! code ELIFECYCLE
  47. [0] npm ERR! [email protected] start-webpack: `better-npm-run start-webpack`
  48. [0] npm ERR! Exit status 1
  49. [0] npm ERR!
  50. [0] npm ERR! Failed at the [email protected] start-webpack script 'better-npm-run start-webpack'.
  51. [0] npm ERR! Make sure you have the latest version of node.js and npm installed.
  52. [0] npm ERR! If you do, this is most likely a problem with the isomorphic-material-relay-starter-kit package,
  53. [0] npm ERR! not with npm itself.
  54. [0] npm ERR! Tell the author that this fails on your system:
  55. [0] npm ERR! better-npm-run start-webpack
  56. [0] npm ERR! You can get information on how to open an issue for this project with:
  57. [0] npm ERR! npm bugs isomorphic-material-relay-starter-kit
  58. [0] npm ERR! Or if that isn't available, you can get their info via:
  59. [0] npm ERR! npm owner ls isomorphic-material-relay-starter-kit
  60. [0] npm ERR! There is likely additional logging output above.
  61. [0]
  62. [0] npm ERR! Please include the following file with any support request:
  63. [0] npm ERR! /home/bogdanbiv/Projects/imrsk/npm-debug.log
  64. [0] npm run start-webpack exited with code 1
  65. --> Sending SIGTERM to other processes..
  66. [1] warn: Checking credentials failed: Authentication token expected: 0.gqvlcwniao979zfr, provided:undefined
  67. [1] warn: Checking credentials failed: Authentication token expected: 802MVIJ9tymWeaNHUqLRfuGsteTOI3vhdhk31s902BT8J0Lta9rNHT9MNVaBfigd9s2974h4RfuGVtbh32o902BT8Jiew29uT913sHU, provided:undefined
  68. [1] warn: Checking credentials failed: Authentication token expected: 802MVIJ9tymWeaNHUqLRfuGsteTOI3vhdhk31s902BT8J0Lta9rNHT9MNVaBfigd9s2974h4RfuGVtbh32o902BT8Jiew29uT913sHU, provided:0.gqvlcwniao979zfr
  69. [1] warn: Checking credentials failed: Authentication token expected: 802MVIJ9tymWeaNHUqLRfuGsteTOI3vhdhk31s902BT8J0Lta9rNHT9MNVaBfigd9s2974h4RfuGVtbh32o902BT8Jiew29uT913sHU, provided:0.gqvlcwniao979zfr
  70. [1] warn: Checking credentials failed: Authentication token expected: 802MVIJ9tymWeaNHUqLRfuGsteTOI3vhdhk31s902BT8J0Lta9rNHT9MNVaBfigd9s2974h4RfuGVtbh32o902BT8Jiew29uT913sHU, provided:0.gqvlcwniao979zfr
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement