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

bebraw · 2016-12-24T07:01:07Z

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 webpack/webpack#3153

DanielaValero · 2017-01-04T09:04:06Z

@ev1stensberg, @pksjce what you guys think, should this be part of our roadmap to v1 ?

bebraw · 2017-01-04T09:11:58Z

Minimum - document how to achieve it outside of the cli. I guess it depends on the overall goals and priority. I expect v1 would be more or less what it is right now and you can build more features in v1.1 and so on.

DanielaValero · 2017-01-04T11:46:02Z

I'd expect the same. So far, did not have time to look deeper into the already available options, but if this is in there, for sure will be part of v1. Otherwise, I'd agree with you by adding this to a v1.1 milestone

evenstensberg · 2017-01-28T13:21:13Z

Fixed #24

nmschulte · 2017-04-06T22:45:25Z

@ev1stensberg, does this apply to hot-module-reloading / webpack-dev-server? I'm looking for a solution to reset Webpack so it'll pick up the new configuration, and have HMR communicate this change appropriately (likely, a "you must manually refresh to pick up latest changes" type message).

How do we enable this in that scenario; is it as simple as watching the files that modify Webpack configuration? How does one use that without causing all watched files to incite a Webpack reset?

evenstensberg · 2017-04-07T09:27:23Z

The resave flag applies to HMR, indeed. Let me get back to you about your issues later this week :)

yacinehmito · 2017-05-17T16:40:13Z

@ev1stensberg How does #24 solve this issue? It seems like it's not related.

evenstensberg · 2017-05-17T17:17:41Z

webpack-cli -w -s will refresh everytime you save. I can see that this is actually for the webpack config itself. Insecure if this can be done on the CLI side of things.

yacinehmito · 2017-05-17T17:28:15Z

IMHO we should either reopen this issue or webpack/webpack#3153

evenstensberg · 2017-05-17T17:32:29Z

Pinging @bebraw for advice

bebraw · 2017-05-17T17:46:03Z

It's about restarting the entire process, yeah. Currently you can sort of pull that off with nodemon or similar.

Maybe it's better to re-open this for now.

scarlac · 2017-09-09T13:22:08Z

The current workaround seems to be, as @bebraw suggests, to use nodemon. I'm doing the following which works at the moment:
nodemon --watch webpack.config.js --exec webpack-dev-server --content-base app/

It's reported by #664, but #664 cannot be fixed fully since watching webpack config changes shouldn't be handled in VuePresss VuePress can only ensure that when user changes the markdown config, the cache identifier will be updated, so user needn't to clean the ./node_modules/.cache muanully. See: webpack/webpack#3153, webpack/webpack-cli#15

It's reported by #664, but #664 cannot be fixed fully since watching webpack config changes shouldn't be handled in VuePresss VuePress can only ensure that when user changes the markdown config, the cache identifier will be updated, so user needn't to clean the ./node_modules/.cache manually. See: webpack/webpack#3153, webpack/webpack-cli#15

sendilkumarn · 2018-12-03T20:16:57Z

@evenstensberg Is this ticket still valid? Can we close this?

evenstensberg · 2018-12-04T09:32:31Z

Still valid, we need to lookup webpack config changes too, doing it in the new version

emilas44 · 2018-12-21T19:07:54Z

Is this implemented already? 17 days has passed from the last post.... I just got here from the link in the book.

yacinehmito · 2018-12-21T20:03:36Z

Is this implemented already? 17 days has passed from the last post.... I just got here from the link in the book.

@emilas44 This issue is open since 2016. It is hardly critical. I don't know what you're expecting in 17 days but know that, as most open source projects, webpack is being made by volunteers an is financed by donations. Neither you nor I am entitled to anything but the freedom to contribute to the project.

lessfish · 2019-10-17T08:06:07Z

@bebraw so has this feature been added to the webpack now?

bebraw · 2019-10-17T08:09:21Z

@lessfish As far as I understand, it didn't happen.

lessfish · 2019-10-17T08:14:21Z

@bebraw sorry to hear that

lessfish · 2019-10-17T08:17:37Z

@bebraw but the issue has been closed, does it mean that the team will not think about this feature?

bebraw · 2019-10-17T08:19:46Z

@lessfish I'm not sure of the current status. I would check webpack 5 release notes. To do this properly, it needs support at the internals.

evenstensberg · 2019-10-19T12:15:52Z

Sorry, gonna reopen, we're gonna support this.

soulofmischief · 2019-10-27T20:05:18Z

@evenstensberg any chance we could have a general solution so that modifying content in additional config folders (i.e. node-config ) could also trigger a change?

evenstensberg · 2019-10-29T16:12:52Z

I think that is a bit out of scope

It's reported by #664, but #664 cannot be fixed fully since watching webpack config changes shouldn't be handled in VuePresss VuePress can only ensure that when user changes the markdown config, the cache identifier will be updated, so user needn't to clean the ./node_modules/.cache manually. See: webpack/webpack#3153, webpack/webpack-cli#15

webpack-bot · 2021-01-15T15:22:00Z

This issue had no activity for at least half a year.

It's subject to automatic issue closing if there is no activity in the next 15 days.

alexander-akait · 2021-01-15T15:25:36Z

bump

evenstensberg · 2021-04-24T18:18:55Z

https://thisdavej.com/how-to-watch-for-files-changes-in-node-js/ and update the webpack options object, do this at a highest level in the architecture as possible. Should be doable

alexander-akait · 2021-04-26T13:05:47Z

No, it is wrong solution, we need watch any require/import and nested require/import

evenstensberg · 2021-06-24T17:58:33Z

No. We need to watch for when the webpack configuration changes, require/import would be the same

alexander-akait · 2021-06-24T18:01:01Z

@evenstensberg if something was changed in require or import we should invalidate configuration again, like we do inside webpack for dependencies

alexander-akait · 2023-05-03T19:42:16Z

Here solution how we can implement this #2797 (comment)

We need:

move buildDependecies from options.cache.buildDependencies to the top option (it will be useful for any configurations, not only for webpack itself)
implement watchRun hook and get files from compilation.modifiedFiles, if we have confiugration file there restart our CLI

evenstensberg · 2023-11-24T18:18:33Z

I think it would be easier to in the first iteration to watch for actual configuration file changes, not the compilation itself

binury · 2023-11-24T18:54:31Z

I think it would be easier to in the first iteration to watch for actual configuration file changes, not the compilation itself

Easier?

evenstensberg · 2023-11-24T19:00:19Z

Yes, implementation wise. We can add cache based invalidation later.

alexander-akait · 2023-12-26T12:48:36Z

We already can implement this if a developer enables cache, we just need

implement watchRun hook and get files from compilation.modifiedFiles, if we have confiugration file there restart our CLI

bebraw mentioned this issue Dec 24, 2016

Watch for config changes webpack/webpack#3153

Closed

bebraw mentioned this issue Jan 2, 2017

Watch webpack.config.js when using the --watch argument webpack/webpack#1899

Closed

DanielaValero changed the title ~~Watch for webpack config changes in watch mode~~ Feature: Watch for webpack config changes in watch mode Jan 3, 2017

evenstensberg added enhancement Feature v2 labels Jan 5, 2017

evenstensberg closed this as completed Jan 28, 2017

mcescalante mentioned this issue Apr 11, 2017

Webpack unable to find ES6 modules after a rename/move/delete preboot/angular-webpack#311

Closed

bebraw reopened this May 17, 2017

evenstensberg mentioned this issue May 19, 2018

[Feature]: Increase memory with a flag / Support Node Flags #289

Closed

ulivz mentioned this issue Jul 25, 2018

Changes to markdown config does not propagate. vuejs/vuepress#664

Closed

parkerziegler mentioned this issue Nov 29, 2018

keyboard shortcut - rebuild FormidableLabs/webpack-dashboard#264

Open

evenstensberg reopened this Oct 19, 2019

robertvansteen mentioned this issue Oct 20, 2019

Get forked react-scripts changes to take effect immediately facebook/create-react-app#7843

Closed

evenstensberg changed the title ~~Feature: Watch for webpack config changes in watch mode~~ [Feature]: Watch for webpack config changes in watch mode Oct 31, 2019

vadzim-revolist mentioned this issue Dec 15, 2019

Is it possible to hot-reload template.yaml? StackToolbox/aws-sam-webpack-plugin#21

Closed

Artur- mentioned this issue Dec 17, 2019

Restart webpack on configuration change vaadin/flow#7184

Open

webpack-bot added the inactive label Jan 15, 2021

webpack-bot removed the inactive label Jan 15, 2021

evenstensberg mentioned this issue Jun 24, 2021

feat: watch mode config change #2797

Closed

hardfist mentioned this issue Jun 7, 2023

Watch config file and auto restart on change web-infra-dev/rspack#3463

Closed

slorber mentioned this issue Jun 20, 2024

Webpack dev server does NOT hot reload (affecting swizzle aliases, prism...) facebook/docusaurus#10238

Open

1 task

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

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

Comments

bebraw commented Dec 24, 2016

DanielaValero commented Jan 4, 2017

bebraw commented Jan 4, 2017

DanielaValero commented Jan 4, 2017

evenstensberg commented Jan 28, 2017 • edited Loading

nmschulte commented Apr 6, 2017

evenstensberg commented Apr 7, 2017

yacinehmito commented May 17, 2017 • edited Loading

evenstensberg commented May 17, 2017

yacinehmito commented May 17, 2017

evenstensberg commented May 17, 2017

bebraw commented May 17, 2017

scarlac commented Sep 9, 2017 • edited Loading

sendilkumarn commented Dec 3, 2018

evenstensberg commented Dec 4, 2018

emilas44 commented Dec 21, 2018 • edited Loading

yacinehmito commented Dec 21, 2018 • edited Loading

lessfish commented Oct 17, 2019

bebraw commented Oct 17, 2019

lessfish commented Oct 17, 2019

lessfish commented Oct 17, 2019

bebraw commented Oct 17, 2019

evenstensberg commented Oct 19, 2019

soulofmischief commented Oct 27, 2019

evenstensberg commented Oct 29, 2019

webpack-bot commented Jan 15, 2021

alexander-akait commented Jan 15, 2021

evenstensberg commented Apr 24, 2021

alexander-akait commented Apr 26, 2021

evenstensberg commented Jun 24, 2021

alexander-akait commented Jun 24, 2021

alexander-akait commented May 3, 2023 • edited Loading

evenstensberg commented Nov 24, 2023

binury commented Nov 24, 2023

evenstensberg commented Nov 24, 2023

alexander-akait commented Dec 26, 2023

evenstensberg commented Jan 28, 2017 •

edited

Loading

yacinehmito commented May 17, 2017 •

edited

Loading

scarlac commented Sep 9, 2017 •

edited

Loading

emilas44 commented Dec 21, 2018 •

edited

Loading

yacinehmito commented Dec 21, 2018 •

edited

Loading

alexander-akait commented May 3, 2023 •

edited

Loading