Remove fsevents from optionalDependencies
See original GitHub issueIs there a reason why fsevents
is in the optional dependencies at the react-scripts package? It’s never used.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How to solve npm install throwing fsevents warning on non ...
json requires fsevent as not optionalDependencies but devDependencies. This may be a problem for non-OSX users. Sometimes. Even if you remove it ...
Read more >npm install error fsevents in Ohter Mac Platforms - Medium
"optionalDependencies": { "fsevents": "*" }. 2 — Another solution would be to ignore optional dependencies during the installation (I got it from search...
Read more >chokidar - npm
If set to false when using fsevents to watch, no more events will be ... handles optional dependencies and is not indicative of...
Read more >node_modules/karma/node_modules/chokidar/package.json
watchFile / fsevents. ... function(path) {console.log('File', path, 'has been removed');})\n .on('unlinkDir', function(path) {console.log('Directory', path, ...
Read more >error found incompatible module. - You.com | The AI Search ...
optionalDependencies : fsevents "^2.0.6". from yarn.lock . Next I removed. "fsevents": "2.0.7",. from resolutions key in package.json.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I looked into this a little more. Chokidar has actually had it as an optionalDependency for a long time, but we added it here for a different reason back when we bundled everything together. We stopped bundling everything together in #1068, but the optionalDependency entry stuck around. So I think it’s ok if we remove it?
react-scripts transitively depends on chokidar through webpack I think.
But maybe you’re right, chokidar added it as an optional dependency in the last year, so it’s possible we don’t need to specify it anymore. I’ll look into it soon.