Bug description

While installing following the instructions on the official page 1 - git clone --depth=1 https://github.com/apache/superset.git

2 - docker compose up --build

I found myself having issues with some node modules as per image

Image

At first I thought that it was my node vesion on my machine, but then I realized that I was buiding Superset with docker, therefore I don't need to have the correct Node version installed on my local machine. How can I solve this?

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
  • [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Comment From: dosubot[bot]

Hi @josedurigon! I'm Dosu and I’m helping the superset team.

This is a common issue on Windows when using Docker Compose with Superset. The root cause is usually the way Docker mounts your local superset-frontend directory into the container. If you have a node_modules folder on your host, or if there are filesystem differences (like case sensitivity or path handling), it can corrupt or interfere with the container’s node_modules, leading to "Module not found" errors for packages like brace and datamaps.world.min. Your local Node version does not affect the build inside Docker, but your local files can if they are mounted into the container citation.

To fix this:

  1. Delete any node_modules folders in your superset-frontend directory on your host machine.
  2. Run docker compose down -v to clear all Docker volumes, then docker compose up --build to rebuild everything from scratch citation.
  3. If you still see errors, try using the compose-non-dev.yml or compose-image-tag.yml files instead of the default compose.yml. These do not mount your local code and use pre-built images, which avoids most Windows filesystem issues citation.
  4. If you need to build frontend assets manually, run npm ci and npm run build inside the superset-frontend directory (either on your host or inside the container) citation.

These steps should resolve most node_modules errors during Docker builds on Windows. If you continue to have issues, double-check that no node_modules folders exist on your host before starting Docker, and avoid switching between host and container npm builds.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

Comment From: HarshithGamini

Highly recommend using Windows Subsystem for Linux (WSL) / Ubuntu for using superset in Windows.

Comment From: msyavuz

@josedurigon Bot's recommendations sound like they might fix your problem, have you tried those?

Comment From: rusackas

Also worth noting we don't officially support Windows, so we might close tickets like this, but we welcome any PRs to add to the docs and help stabilize things that needs touch-ups and workarounds.