Skip to content
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

Optionally install fsevents module to prevent 100% CPU load on macOS (#12368) #12370

Merged
merged 1 commit into from
May 3, 2017

Conversation

jsnajdr
Copy link
Member

@jsnajdr jsnajdr commented Mar 21, 2017

Add fsevents module as an optional (macOS) dependency. When this module is installed,
webpack-dev-server watches the project files without polling and doesn't consume CPU.

…12368)

Add fsevents module as an optional (macOS) dependency. When this module is installed,
webpack-dev-server watches the project files without polling and doesn't consume CPU.
@samouri
Copy link
Contributor

samouri commented Mar 21, 2017

I love this idea. My one question is, how does this play with shrinkwrap? Do we need to change any of our scripts to install using --no-optional?
sources:

@jsnajdr
Copy link
Member Author

jsnajdr commented Mar 21, 2017

Hmmm, I'll have to research how this interacts with npm shrinkwrap. One question to make sure I understand the problem: If we leave the PR as it is, then npm install --production will install also the fsevents module, right? But it shouldn't, because it's in fact a dev dependency. Is that the problem? Or anything else?

@matticbot matticbot added the [Size] S Small sized issue label Mar 27, 2017
@lancewillett lancewillett added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Apr 6, 2017
@gwwar
Copy link
Contributor

gwwar commented May 2, 2017

Do we need to change any of our scripts to install using --no-optional

No updates are needed for the shrinkwrap generation, we already install using --no-optional in the script

See also #5386

@jsnajdr
Copy link
Member Author

jsnajdr commented May 3, 2017

No updates are needed for the shrinkwrap generation, we already install using --no-optional in the script

@gwwar Does this mean that there are no obstacles to merging this PR? Running make shrinkwrap doesn't make any relevant changes to the npm-shrinkwrap.json file -- just minor version updates to some unrelated packages.

@jsnajdr jsnajdr self-assigned this May 3, 2017
@jsnajdr jsnajdr requested a review from gwwar May 3, 2017 10:44
@samouri
Copy link
Contributor

samouri commented May 3, 2017

🚢 , this all LGTM!.

@samouri samouri added [Status] Ready to Merge and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels May 3, 2017
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.

None yet

6 participants