[Feature]: Watch for webpack config changes in watch mode

Open
#15 42 comments 48 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, webpack
Domain
build-system, cli

Research direction

No file or test is named; begin at webpack-cli's watch-mode entry point and inspect how webpack configuration and its dependencies are watched. Reproduce a configuration or loader/PostCSS option change in the stated webpack 2.x setup, then verify watch mode rebuilds without restarting the current process.

Written by the indexing model from the issue text.

Description

enhancement Feature Up for planning

I'm submitting a feature request

Webpack version:
2.x

Please tell us about your environment:
OSX 10.x

Current behavior:
I'm not sure if this was discussed before, but it's one of the pain point for me in webpack workflow.

When config / config's dep is updated — hot reloadable server (or watch mode) must be restarted manually. Usually this hot reloadable server is not stand-alone process, but part of the bigger task or even lives inside docker container. And in case of config related change — the only way to pick this up is to restart everything.

Expected/desired behavior:

It'd be cool if webpack could track such changes and rebuild everything from scratch w/o killing current process.

What is the motivation / use case for changing the behavior?

It'll make easier:

  • work on webpack config setup
  • work w/ loader's configs, eg postcss plugin's options (js vars etc)

Moved from https://github.com/webpack/webpack/issues/3153

Dominant language
JavaScript
Stars
2.6k
Forks
678
Avg merge
17h 42m
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from webpack/webpack-cli

All issues in webpack/webpack-cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.