dosubot[bot] commented on issue #34225: URL: https://github.com/apache/superset/issues/34225#issuecomment-3090116561
<!-- Greeting --> Hi @josedurigon! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> 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](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker-compose.yml). 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](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/docker/README.md). 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](https://github.com/apache/superset/pull/33790). 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](https://github.com/apache/superset/issues/32821). 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. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b5640aaa-9bff-4a64-84cb-8dbc6451ae43?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34225) -- 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]
