Skip to content

fix: don't check all node_modules from checkForChanges method #4671

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

Merged
merged 6 commits into from
Jun 6, 2019

Conversation

Fatme
Copy link
Contributor

@Fatme Fatme commented Jun 3, 2019

Rel to: #4647

PR Checklist

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

@cla-bot cla-bot bot added the cla: yes label Jun 3, 2019
Fatme added 4 commits June 5, 2019 11:57
modulesChange property was used to indicate .js change in node_modules but webpack watches for changes in `.js` files from node_modules if they are required in application, so no more need from this property.
@Fatme Fatme force-pushed the fatme/project-changes branch from f9850cb to 5f50f67 Compare June 5, 2019 12:27
Chokidar raises changed event when `.js` file is changed from within symlinked plugin and this led to a native build on every .js change for plugin's developer. As a workaround, we checked if there are native changes and rebuild the project only in this case.
@Fatme Fatme force-pushed the fatme/project-changes branch from 5f50f67 to 7e79e0b Compare June 5, 2019 13:06
@Fatme Fatme merged commit edd0fae into feature/webpack-only Jun 6, 2019
@Fatme Fatme deleted the fatme/project-changes branch June 6, 2019 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants