-
Notifications
You must be signed in to change notification settings - Fork 756
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
Chokidar or Anymatch for glob patterns? #1122
Comments
To exclude directories though, do the following. browsersync.init({
files: [
{
options: {
ignoreInitial: false,
ignored: [
/bower_components|node_modules/
]
},
match: [serverPath + '**.html'],
fn: onHTMLChange
}
]
}); |
@shakyShane Thanks I figured that along the way. But then is it a bug on the documentation, because anymatch accept this kind of pattern? I got a bit confused that it mentions anymatch at all instead chokidar? |
shakyShane
added a commit
that referenced
this issue
Jun 7, 2016
Removed from https://www.browsersync.io/docs/options |
This was referenced Jun 7, 2016
This was referenced Jul 31, 2016
This was referenced Oct 18, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue details
The documentation states that for the
files
attribute under browsersync options, that I can use patterns following Anymatch api.However when using functions or anything that is not a string within
files[n].match
, I get an error:Steps to reproduce/test case
Please specify which version of Browsersync, node and npm you're running
Affected platforms
Browsersync use-case
The text was updated successfully, but these errors were encountered: