Skip to content

Webpack not found #9085

@alexbeletsky

Description

@alexbeletsky

Application hangs after login with admin account.

Expected results

The application is up and running

Actual results

The application stuck right after login:

Screenshot 2020-02-04 at 18 06 09

How to reproduce the bug

  1. git clone
  2. docker-compose up
  3. open http://localhost:8088/
  4. 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    | > [email protected] 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! [email protected] 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 [email protected] dev script.
superset-node_1    | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    inactiveInactive for >= 30 days

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions