Watching for changes on files with lots of `@import`s had a significant regression in responsiveness in #1745. The regression was caused by calling `gaze.add` unnecessarily. We only need to call `gaze.add` on files that aren't currently being watched. At the time I confirmed that calling `gaze.add` in files that were being watched wouldn't result in a leak or multiple events being fired. I however assumed calling `gaze.add` for already watched files would be very cheap. Fixes #1869
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| lib | Loading commit data... | |
| media | Loading commit data... | |
| scripts | Loading commit data... | |
| src | Loading commit data... | |
| test | Loading commit data... | |
| .editorconfig | Loading commit data... | |
| .eslintrc.json | Loading commit data... | |
| .gitattributes | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| ISSUE_TEMPLATE.md | Loading commit data... | |
| LICENSE | Loading commit data... | |
| README.md | Loading commit data... | |
| TROUBLESHOOTING.md | Loading commit data... | |
| appveyor.yml | Loading commit data... | |
| binding.gyp | Loading commit data... | |
| package.json | Loading commit data... |