-
Notifications
You must be signed in to change notification settings - Fork 40
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
Add option for the theme listener to ignore paths specified by the user #280
Add option for the theme listener to ignore paths specified by the user #280
Conversation
👋 Friendly bump on this. Would you have a moment to check this out? /cc @ocke @sarmadsangi (and whoever else owns this project) |
Bumping again. Can we update the PR instructions to make sure that outside users can successfully contribute to this open source project? Right now there isn't a way to get the maintainers' attention (see: #281). I would like to get this merged or at least considered and not have to continue to support my fork as a dependency on our end. |
Hey @jakebellacera. Sorry for the last response and thanks for the contribution. Do you think we should make zat always ignore |
@ocke no worries! A default list with |
Hi @jakebellacera, we force updated master branch so can you please rebase your PR? Thank you 🙇 |
@jakebellacera sorry for missing out on this PR. This is great 🎉 We have seen similar issues with Suggested solution
What do you think? |
74d23a6
to
e93d1dc
Compare
@hoangtrvu updated! @sarmadsangi the |
797ccf0
to
79180e0
Compare
@augustocravosilva can we get a review and approval from your team for this change? |
This would be really good to get in. At the moment I'm blocked from being able to manage my dependencies using Yarn/NPM |
Bump. Any updates? |
I'm deciding to close this PR since it doesn't look like it's going to get through. If plans change, I'm happy to reopen. |
✌️
/cc @zendesk/vegemite
Description
The theme listener watches all files in the directory, so when working with a project with a large
node_modules
for instance, this can cause the watcher to perform very slowly. Another issue this solves is that multiple instances of guard can co-exist within the working directory in case you have gulp/webpack watching thesrc
folder, for example.How it works
Users can specify an
--ignore
option to have the listener explicitly ignore an array of paths. Example: