aortiz-WW commented on issue #22829:
URL: https://github.com/apache/superset/issues/22829#issuecomment-1405422088

   
   > Closing since it's not a bug, but a developer experience issue. I assure 
you, it does work!
   > 
   > When running the vanilla `docker-compose up` in your terminal, and you 
make a file change in the frontend directory, you'll see in your terminal that 
Webpack starts rebuilding. This takes time! You will not see the changes right 
away, but they will happen, and you will need to refresh the browser when they 
do.
   > 
   > Also, you can start a second terminal process, cd into `superset-frontend` 
and do `npm run dev-server`. This runs a dev mode process (with hot reloading) 
that proxies to your original Superset server process, and runs on port 9000 
instead. However, this means you have TWO webpack builds running concurrently, 
so you might want to turn off the original docker webpack process by commenting 
out a line in the `docker-frontend` file.
   > 
   > Hope that helps!
   
   How much time would you say? In my case, I have waited more than half an 
hour and nothing happened
   


-- 
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]

Reply via email to