Front-end changes not reflecting in superset

Superset Version: 0.36.0 OS: Ubuntu 16.04 LTS node version: 12.18.2 npm version: 6.14.5

When I try to make changes in superset frontend and then build those changes in dev server by running the command in incubator-superset/superset-frontend

npm install npm install webpack npm run dev-server

I get this error: When I view log file, I get this:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'dev-server' ]
2 info using npm@6.14.5
3 info using node@v12.18.2
4 verbose run-script [ 'predev-server', 'dev-server', 'postdev-server' ]
5 info lifecycle superset@0.999.0-dev~predev-server: superset@0.999.0-dev
6 info lifecycle superset@0.999.0-dev~dev-server: superset@0.999.0-dev
7 verbose lifecycle superset@0.999.0-dev~dev-server: unsafe-perm in lifecycle true
8 verbose lifecycle superset@0.999.0-dev~dev-server: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/s$
9 verbose lifecycle superset@0.999.0-dev~dev-server: CWD: /home/shivam/apache_superset/incubator-superset/superset-frontend
10 silly lifecycle superset@0.999.0-dev~dev-server: Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'NODE_ENV=development BABEL_ENV=development node --max_old_space_size=4096 ./node_modules/webpack-dev-server/bin/webp$
10 silly lifecycle ]
11 silly lifecycle superset@0.999.0-dev~dev-server: Returned: code: 137  signal: null
12 info lifecycle superset@0.999.0-dev~dev-server: Failed to exec dev-server script
13 verbose stack Error: superset@0.999.0-dev dev-server: `NODE_ENV=development BABEL_ENV=development node --max_old_space_size=4096 ./node$
13 verbose stack Exit status 137
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/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> (/usr/local/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 superset@0.999.0-dev
15 verbose cwd /home/shivam/apache_superset/incubator-superset/superset-frontend
16 verbose Linux 5.3.0-1030-gcp
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "dev-server"
18 verbose node v12.18.2
19 verbose npm  v6.14.5
20 error code ELIFECYCLE
21 error errno 137
22 error superset@0.999.0-dev dev-server: `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 137
23 error Failed at the superset@0.999.0-dev dev-server script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 137, true ]

[sedhha]

So basically superset freezes here: I tried checking 9000 port hoping that maybe it’s running but it’s not.

I had one big question, git clone <superset git repository> is only if you have docker right? When I did a venv installation, i didn’t find any superset-frontend folder. To build the changes in venv based installation as per the instructions where should we run the above commands to see the changes? Just curious, since there’s no such directory when the installation is done virtually.

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.87. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.