Skip to content
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

Closed
luca-moser opened this issue Apr 10, 2015 · 6 comments
Closed

Allow multi wildcards for watchedFiles property #426

luca-moser opened this issue Apr 10, 2015 · 6 comments

Comments

@luca-moser
Copy link

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 like models\**\*.js crashes IISNode.

@donatasbacius
Copy link

+1

2 similar comments
@dfoverdx
Copy link

dfoverdx commented Feb 1, 2016

+1

@dsbudiac
Copy link

+1

@rramachand21-zz
Copy link
Collaborator

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.

@ayyash
Copy link

ayyash commented Nov 1, 2016

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?

@mac2000
Copy link

mac2000 commented Jul 8, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants