-
Notifications
You must be signed in to change notification settings - Fork 588
-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multi wildcards for watchedFiles property #426
Comments
+1 |
2 similar comments
+1 |
+1 |
Please code this up in your java script code as every app wants different capability with watched files. You can watch files within your app however you want and then finally update one file that iisnode is looking for. |
You mean (for example): gulp watch server/*/.js to recreate ./server.js? if there is nothing to update in that file, would iis still pick up the recreation and trigger a restart? |
JFYI: just went back from my dynamic webpack entry point journey with some results https://github.com/mac2000/webpack-dynamic-entry-demo hope it will help someone else also, in our case idea is that we have always running IIS web site which compiles requested file on the fly, so developer do not need to start and/or restart anything, just turn on PC and start coding and having fun it is just to demonstrate one of possible ways how it can be done even without file watchers |
Hi Tomasz,
I want to be able to declare paths like
models\**\*.js
for watchedFiles in web.config since I don't want to enter each sub directory manually to the list of watched files. Currently only*.js
is working. Using a wildcard directory entry likemodels\**\*.js
crashes IISNode.The text was updated successfully, but these errors were encountered: