Webpack not found

[alexbeletsky]

Application hangs after login with admin account.

Expected results

The application is up and running

Actual results

The application stuck right after login:

How to reproduce the bug

0. git clone
1. docker-compose up
2. open http://localhost:8088/
3. login with admin/admin

Environment

(please complete the following information):

• superset version: current master 540df26
• python version: python --version
• node.js version: node -v
• npm version: npm -v

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

superset-node_1    | audited 906857 packages in 74.627s
superset-node_1    |
superset-node_1    | 1 package is looking for funding
superset-node_1    |   run `npm fund` for details
superset-node_1    |
superset-node_1    | found 2 moderate severity vulnerabilities
superset-node_1    |   run `npm audit fix` to fix them, or `npm audit` for details
superset-node_1    |
superset-node_1    | > superset@0.999.0-dev dev /app/superset/assets
superset-node_1    | > webpack --mode=development --colors --progress --debug --watch
superset-node_1    |
superset-node_1    | sh: 1: webpack: not found
superset-node_1    | npm ERR! code ELIFECYCLE
superset-node_1    | npm ERR! syscall spawn
superset-node_1    | npm ERR! file sh
superset-node_1    | npm ERR! errno ENOENT
superset-node_1    | npm ERR! superset@0.999.0-dev dev: `webpack --mode=development --colors --progress --debug --watch`
superset-node_1    | npm ERR! spawn ENOENT
superset-node_1    | npm ERR!
superset-node_1    | npm ERR! Failed at the superset@0.999.0-dev dev script.
superset-node_1    | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

[willbarrett]

Hi @alexbeletsky - thanks for the report. I just ran into this problem myself this AM. I'm trying to find the source of the problem now.

[saltict]

@alexbeletsky I have same issue like you and I resolved it.

You need to replace line command of superset-node in docker compose with this:
command: ["bash", "-c", "cd /app/superset-frontend && npm install --global webpack webpack-cli && npm install && npm run dev"]

[willbarrett]

Thanks for the suggestion @saltict - I've opened a PR with the change.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.