This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 639
watch.ts is causing ENOENT #53
Comments
Just figured out that it should be possible to disable the temporary file creation of webstorm since another project had the same issue reported: arboleya/coffee-toaster#57 Nevermind, it might be useful to have some kind of restriction for the watch process. What do you think? |
The issue seems out of scope for the project. For support questions please ask in gitter, twitter, or stack overflow. I'll be closing this for now to keep the issues down |
That's fine, @gdi2290 . I found the solution and would like to share it (taken from arboleya/coffee-toaster#57 (comment)): It is possible to disable temporary file creation in WebStorm as follows:
|
And with Webstorm 2016.1:
|
Can you add this to the wiki? Thanks! |
I can't access the wiki. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Running npm start and having all source files watched to make browsersync work, I occasionally encounter errors that terminate the entire gulp process. I assume it's my IDE (webstorm) that may for a short time create temporary files leading to:
It would be great to have the watch process only watch for a defined set of file types (maybe make it configurable in config/seed.config.ts or config/project.config.ts). I don't have a good solution, but my temporary workaround for this issue results in a change to watch.ts:
The text was updated successfully, but these errors were encountered: