FSEvents support
Open
Nobody has claimed this yet.
bug
package issue
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
This is currently a blocking issue on the next.js integration.
Error is with Webpack's use of FSEvents in the watcher:
TypeError: fsevents is not a constructor
at createFSEventsInstance (/Users/timneutkens/projects/sandbox/abc/node_modules/next/dist/compiled/webpack/webpack.js:18980:11)
at setFSEventsListener (/Users/timneutkens/projects/sandbox/abc/node_modules/next/dist/compiled/webpack/webpack.js:19034:16)
at FSWatcher.module.exports.1043.FsEventsHandler._watchWithFsEvents (/Users/timneutkens/projects/sandbox/abc/node_modules/next/dist/compiled/webpack/webpack.js:19204:16)
at FSWatcher.<anonymous> (/Users/timneutkens/projects/sandbox/abc/node_modules/next/dist/compiled/webpack/webpack.js:19338:25)
at LOOP (fs.js:1585:14)
at processTicksAndRejections (internal/process/next_tick.js:74:9)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Next.js integration failure and start at webpack.js functions createFSEventsInstance, setFSEventsListener, and FsEventsHandler._watchWithFsEvents named in the stack trace. Check the FSEvents compatibility at that path; done means the watcher starts without the reported TypeError in the integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, next.js, webpack
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100