This repository has been archived by the owner on Aug 4, 2021. It is now read-only.
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.
This is a first attempt at updating to the new micromatch 4. My fear is that this would be a breaking update as I think I have spotted some object rest/spread operators in its dependencies, but we will see what CI says on Node 6. Otherwise I wonder if we should consider moving the "createFilter" functionality to core Rollup (and make it throw if we are on a browser build) as there, we could use TypeScript to transpile the spread operators to something more downward compatible.