You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work in a large monorepo, so when I launch the Webpack dev server, the localhost URL is unpredictable. Different apps may use different ports.
Webpack helpfully prints the URL into the console log, so that you can easily click on it to launch the Chrome web browser. It looks like this:
Currently this message is only printed once. After several incremental rebuilds, the message scrolls off the screen and gets lost. The workaround is to kill and restart the dev server, but for large projects this can mean waiting several minutes for initialization.
Suggested improvement: After every incremental rebuild, print the URL last.
Suggested improvement: After every incremental rebuild, print the URL last.
We've done this before but got a lot of feedback that it gets in the way, so we did it once, I'm afraid we can't please everyone, maybe only under the option
Feature Proposal
I work in a large monorepo, so when I launch the Webpack dev server, the localhost URL is unpredictable. Different apps may use different ports.
Webpack helpfully prints the URL into the console log, so that you can easily click on it to launch the Chrome web browser. It looks like this:
Currently this message is only printed once. After several incremental rebuilds, the message scrolls off the screen and gets lost. The workaround is to kill and restart the dev server, but for large projects this can mean waiting several minutes for initialization.
Suggested improvement: After every incremental rebuild, print the URL last.
How should this be implemented
A minor change to the logging code:
webpack-dev-server/lib/Server.js
Feature Use Case
This change would make Webpack Dev Server easier to use.
Please paste the results of
npx webpack-cli info
here, and mention other relevant informationThe text was updated successfully, but these errors were encountered: