browserify / browserify/watchify
watchify ignores paths option passed to browserify on update
Open
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 178
- PR merge metrics
- No merged PRs in 30d
Description
When watchify fires the 'update' event, calling b.bundle() produces errors that would not happen if b.paths option was being taken into account - indeed, the bundle compiles the first time around because of this.
This error can only be observed when saving a file within a local npm module that has been symlinked into the node_modules folder of an app.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.