webpack / webpack/webpack-dev-server
show lazyCompilation information while compiling in the client overlay
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.8k
- Forks
- 1.5k
- Avg merge
- 5h 32m
- Merged PRs (30d)
- 6
Description
Feature Proposal
I'd like to provide some feedback to developers while webpack is compiling when using lazyCompilation experimental feature
Feature Use Case
just improve the dx, not thinking that something is broken
Please paste the results of npx webpack-cli info here, and mention other relevant information
System:
OS: macOS 12.1
CPU: (4) x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
Memory: 63.11 MB / 16.00 GB
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: 1.22.17 - ~/Dev/entria/feedback/feedback-admin/node_modules/.bin/yarn
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
Monorepos:
Yarn Workspaces: 1.22.17
Lerna: 4.0.0
Packages:
eslint-import-resolver-webpack: 0.13.2 => 0.13.2
webpack-merge: 5.8.0 => 5.8.0
webpack-node-externals: 3.0.0 => 3.0.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the client overlay and the lazyCompilation handling in webpack-dev-server. Determine what compilation information is available and how it should be presented to developers, then verify the overlay reports useful progress while compilation is in progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100