-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
exclude /node_modules/ from _watch by default (#1794)
- Loading branch information
Showing
3 changed files
with
84 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
4c52153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re:
lib/Server.js
, line 121+.I can understand the decision to ignore changes in
node_modules/
by default, but this could cause problems for Lerna users who haveresolve.symlinks
set tofalse
. I need this setting for Vue.js and TypeScript to play nicely. Resolving symlinks seems, to me, like an odd thing for webpack to do to begin with, but that's another topic.The point is, I have common component and style packages under
node_modules/
(vianpm link
), which will appear as such to the dev server withsymlinks: false
. This new configuration will therefore ignore any changes in those common packages.Does this new default bring a significant performance gain? I don't object to the change, but it took me a day to find this little commit. Some documentation should probably be brought up to date. I can do that, but I don't know how tightly coupled
devServer
and webpack-dev-server are allowed to be. Should this default perhaps live in webpack, and therefore be passed to any potential development server (webpack-serve? 🙃).I now have:
4c52153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blieque thank you for your feedback. Please submit the monorepo.
4c52153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hiroppy Thanks for the quick reply! Sorry, this is in an internal repository. The configuration I posted does work though. I can set up a demo repository if that would help you, but this will take a little while.
I think the ideal solution may be for webpack to always resolve symlinks when performing this check regardless of
resolve.symlinks
.4c52153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's speak about this here #1934