Reset current compilation if file was changed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, webpack
- Domain
- build-system, tooling
Research direction
Reproduce this with koa-webpack and webpack-dev-middleware by changing a file, waiting two seconds, and changing it again. Trace how the active compilation and the next compilation are scheduled, then verify that the current compilation is reset and the latest change starts a new compilation immediately.
Written by the indexing model from the issue text.
Description
The Issues page for this repository is not a support forum. Please ask questions on StackOverflow or the webpack Gitter (https://gitter.im/webpack/webpack). Questions will be closed. If you proceed with this form, please fill out all fields, or your issue may be closed as "invalid." Please do not delete this template from a new issue. Please remove this header to acknowledge this message.
- Operating System: Mac OS 10.12.4
- Node Version: 8.11.2
- NPM Version: 5.6.0
- webpack version: 4.29.3
- webpack-dev-middleware Version: 3.5.2
- [] This is a feature request
- This is a bug
Expected Behavior
Current active compilation should reset if file was changed and next compilation should start immediate
Actual Behavior
Current active compilation will finish first if file was changed and only after that - next compilation will start
For Bugs; How can we reproduce the behavior?
I'm using latest koa-webpack + webpack@4.
Start server, change file, after two seconds change file again. As result - two full compilations instead of 2 seconds of first compilation + full second compilation.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 380
- Avg merge
- 3h 16m
- Merged PRs (30d)
- 14
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.
More from webpack/webpack-dev-middleware
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
webpack/webpack-dev-middleware#2407 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
webpack/webpack-dev-middleware#1229 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
webpack/webpack-dev-middleware#979 · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
webpack/webpack-dev-middleware#861 · 20 comments · 21 reactions ·
All issues in webpack/webpack-dev-middleware
Similar issues
-
curation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
amponce/archive-movie-browser#186 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
clerk/javascript#9852 ·
-
bug p1 tools
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100