gk1089 commented on issue #18615:
URL: https://github.com/apache/superset/issues/18615#issuecomment-1037867933
I am still stuck. I realized that most of my issues are due to being behind
a proxy since I still don't know how I can change the proxy settings for npm to
make npm work inside of a docker container.
So today I am trying to set a dev server in a VM on my laptop directly
connected to the internet without the proxy issues. I will still need to figure
stuff out to make it work for the office environment behind proxy for long term.
Anyway, even without the proxy, I am getting stuck at the `npm run
dev-server` command while the `docker-compose up` is merrily running its loop.
> 10% building 0/1 entries 0/0 dependencies 0/0 modules[webpack-cli]
/home/rrscw/superset/superset-frontend/node_module
s/webpack-dev-server/lib/servers/WebsocketServer.js:10
> static heartbeatInterval = 1000;
> ^
>
> SyntaxError: Unexpected token =
> at new Script (vm.js:83:7)
> at NativeCompileCache._moduleCompile
(/home/rrscw/superset/superset-frontend/node_modules/v8-compile-cache/v8-com
pile-cache.js:240:18)
> at Module._compile
(/home/rrscw/superset/superset-frontend/node_modules/v8-compile-cache/v8-compile-cache.js:184:
36)
> at Object.Module._extensions..js
(internal/modules/cjs/loader.js:789:10)
> at Module.load (internal/modules/cjs/loader.js:653:32)
> at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
> at Function.Module._load (internal/modules/cjs/loader.js:585:3)
> at Module.require (internal/modules/cjs/loader.js:692:17)
> at require
(/home/rrscw/superset/superset-frontend/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
> at Server.getServerTransport
(/home/rrscw/superset/superset-frontend/node_modules/webpack-dev-server/lib/Server.j
s:1009:28)
> npm ERR! code ELIFECYCLE
> npm ERR! errno 2
> npm ERR! [email protected] dev-server: `cross-env NODE_ENV=development
BABEL_ENV=development node --max_old_space_si
ze=4096 ./node_modules/webpack-dev-server/bin/webpack-dev-server.js
--mode=development`
> npm ERR! Exit status 2
> npm ERR!
> npm ERR! Failed at the [email protected] dev-server script.
> npm ERR! This is probably not a problem with npm. There is likely
additional logging output above.
>
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2022-02-13T06_48_45_404Z-debug.log
> root@rrscw:/home/rrscw/superset/superset-frontend# node
/root/.npm/_logs/2022-02-13T06_48_45_404Z-debug.log
The log file says:
> 0 info it worked if it ends with ok
> 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'dev-server' ]
> 2 info using [email protected]
> 3 info using [email protected]
> 4 verbose run-script [ 'predev-server', 'dev-server', 'postdev-server' ]
> 5 info lifecycle [email protected]~predev-server: [email protected]
> 6 info lifecycle [email protected]~dev-server: [email protected]
> 7 verbose lifecycle [email protected]~dev-server: unsafe-perm in
lifecycle true
> 8 verbose lifecycle [email protected]~dev-server: PATH:
/usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/rrscw/superset/superset-frontend/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/g>
> 9 verbose lifecycle [email protected]~dev-server: CWD:
/home/rrscw/superset/superset-frontend
> 10 silly lifecycle [email protected]~dev-server: Args: [ '-c',
> 10 silly lifecycle 'cross-env NODE_ENV=development BABEL_ENV=development
node --max_old_space_size=4096
./node_modules/webpack-dev-server/bin/webpack-dev-server.js --mode=development'
]
> 11 silly lifecycle [email protected]~dev-server: Returned: code: 2
signal: null
> 12 info lifecycle [email protected]~dev-server: Failed to exec dev-server
script
> 13 verbose stack Error: [email protected] dev-server: `cross-env
NODE_ENV=development BABEL_ENV=development node --max_old_space_size=4096
./node_modules/webpack-dev-server/bin/webpack-dev-server.js --mode=development`
> 13 verbose stack Exit status 2
> 13 verbose stack at EventEmitter.<anonymous>
(/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
> 13 verbose stack at EventEmitter.emit (events.js:198:13)
> 13 verbose stack at ChildProcess.<anonymous>
(/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
> 13 verbose stack at ChildProcess.emit (events.js:198:13)
> 13 verbose stack at maybeClose (internal/child_process.js:982:16)
> 13 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:259:5)
> 14 verbose pkgid [email protected]
> 15 verbose cwd /home/rrscw/superset/superset-frontend
> 16 verbose Linux 5.4.0-99-generic
> 17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "dev-server"
> 18 verbose node v10.19.0
> 19 verbose npm v6.14.4
> 20 error code ELIFECYCLE
> 21 error errno 2
> 22 error [email protected] dev-server: `cross-env NODE_ENV=development
BABEL_ENV=development node --max_old_space_size=4096
./node_modules/webpack-dev-server/bin/webpack-dev-server.js --mode=development`
> 22 error Exit status 2
> 23 error Failed at the [email protected] dev-server script.
> 23 error This is probably not a problem with npm. There is likely
additional logging output above.
> 24 verbose exit [ 2, true ]
I have no clue what is going on at this point.
Help!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
