Only handle '.css' files in writeFile #173
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Chokidar can trigger `writeFile` for files that `glob()` does not, so add extra precaution here to skip avoidable error logs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Chokidar can trigger
writeFilefor files thatglob()does not (see example of issue in screenshot).In our case, starting
watchon patternpackages/**/*.module.cssin a monorepo has chokidar trigger for files like:packages/apps/WebApp/node_modules/.bin/lint-stagedpackages/apps/WebApp/node_modules/.bin/prettierIt seems that the issue is caused by
chokidarusingglob-parentthat handles recursive patterns in a different way thanglob.Solution
Adding an extra precaution that checks
.cssextension before writing file to skip avoidable error logs.Not perfect but feels ok to require
.css-extension in this module.Error screenshot