-
-
Notifications
You must be signed in to change notification settings - Fork 200
feat: configure watching options #486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
6751e5e
to
e6eb6e1
Compare
Hi @Kocal,
That being said... I'm wondering if we shouldn't have a |
Watch mode can be used without a dev-server, so I think it's better to have a |
Don't worry about the failing tests, they are not related to your PR :) You don't have them locally because they are in a Travis job that tests the highest possible version of the dependencies (it removes the lock file before downloading them) and sometimes Webpack changes something that causes the hardcoded hashes from our functional tests to become outdated. |
Oh okay, thanks for the explanation 👍 |
Who is ready for a new review? 😺 |
Thank you @Kocal |
Yep! :) |
This PR adds support for properly configuring watching options.
References: #35, #126
Before, we had to do this:
Now, we can do this:
Also, I think it would be better to rename it to
configureWatchOptions()
, but I don't know how encore apply watching options to webpack when running dev or prod environment withencore [prod|dev] --watch
. 🤔Thanks!
EDIT: Ah, I found it!

I will see how can I modify
watchOptions
in dev/prod modes.