I am working on the homework for Wk 4 with python coding. I got this error on the command line in Gitpod after running npm run start (entire log below)
22 error getting-started-with-apollo-ui@1.0.0 start: `cross-env NODE_ENV=development webpack-dev-server -d` 22 error Exit status 1 0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/home/gitpod/.nvm/versions/node/v12.18.3/bin/node', 1 verbose cli '/home/gitpod/.nvm/versions/node/v12.18.3/bin/npm', 1 verbose cli 'run', 1 verbose cli 'start' 1 verbose cli ] 2 info using npm@6.14.7 3 info using node@v12.18.3 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle getting-started-with-apollo-ui@1.0.0~prestart: getting-started-with-apollo-ui@1.0.0 6 info lifecycle getting-started-with-apollo-ui@1.0.0~start: getting-started-with-apollo-ui@1.0.0 7 verbose lifecycle getting-started-with-apollo-ui@1.0.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle getting-started-with-apollo-ui@1.0.0~start: PATH: /home/gitpod/.nvm/versions/node/v12.18.3/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/workspace/cassandra-workshop-series/week4-AppDev-api/getting-started-with-astra-ui/node_modules/.bin:/home/gitpod/.nvm/versions/node/v12.18.3/bin:/home/gitpod/.cargo/bin:/home/gitpod/.pyenv/plugins/pyenv-virtualenv/shims:/home/gitpod/.pyenv/shims:/workspace/.cargo/bin:/workspace/.pip-modules/bin:/workspace/.rvm/bin:/home/gitpod/.cargo/bin:/home/gitpod/.sdkman/candidates/maven/current/bin:/home/gitpod/.sdkman/candidates/java/current/bin:/home/gitpod/.sdkman/candidates/gradle/current/bin:/home/gitpod/.cargo/bin:/home/gitpod/.rvm/gems/ruby-2.6.6/bin:/home/gitpod/.rvm/gems/ruby-2.6.6@global/bin:/home/gitpod/.rvm/rubies/ruby-2.6.6/bin:/home/gitpod/.pyenv/plugins/pyenv-virtualenv/shims:/home/gitpod/.pyenv/shims:/workspace/.cargo/bin:/workspace/.pip-modules/bin:/workspace/.rvm/bin:/home/gitpod/.pyenv/bin:/home/gitpod/.pyenv/shims:/workspace/go/bin:/home/gitpod/go/bin:/home/gitpod/go-packages/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin/:/home/gitpod/.nvm/versions/node/v12.18.3/bin:/home/gitpod/.rvm/bin:/home/gitpod/.rvm/bin:/home/gitpod/.rvm/bin 9 verbose lifecycle getting-started-with-apollo-ui@1.0.0~start: CWD: /workspace/cassandra-workshop-series/week4-AppDev-api/getting-started-with-astra-ui 10 silly lifecycle getting-started-with-apollo-ui@1.0.0~start: Args: [ '-c', 'cross-env NODE_ENV=development webpack-dev-server -d' ] 11 silly lifecycle getting-started-with-apollo-ui@1.0.0~start: Returned: code: 1 signal: null 12 info lifecycle getting-started-with-apollo-ui@1.0.0~start: Failed to exec start script 13 verbose stack Error: getting-started-with-apollo-ui@1.0.0 start: `cross-env NODE_ENV=development webpack-dev-server -d` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/home/gitpod/.nvm/versions/node/v12.18.3/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 13 verbose stack at EventEmitter.emit (events.js:315:20) 13 verbose stack at ChildProcess.<anonymous> (/home/gitpod/.nvm/versions/node/v12.18.3/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at ChildProcess.emit (events.js:315:20) 13 verbose stack at maybeClose (internal/child_process.js:1021:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5) 14 verbose pkgid getting-started-with-apollo-ui@1.0.0 15 verbose cwd /workspace/cassandra-workshop-series/week4-AppDev-api/getting-started-with-astra-ui 16 verbose Linux 4.14.138+ 17 verbose argv "/home/gitpod/.nvm/versions/node/v12.18.3/bin/node" "/home/gitpod/.nvm/versions/node/v12.18.3/bin/npm" "run" "start" 18 verbose node v12.18.3 19 verbose npm v6.14.7 20 error code ELIFECYCLE 21 error errno 1 22 error getting-started-with-apollo-ui@1.0.0 start: `cross-env NODE_ENV=development webpack-dev-server -d` 22 error Exit status 1 23 error Failed at the getting-started-with-apollo-ui@1.0.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]