Prebundle PostCSS plugins for minifyCSS option #315
Merged
Conversation
This file contains 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
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.
This PR is trying to bundle PostCSS plugins used by
minifyCSSoption into Marp Core.These plugins (from cssnano project) are designed for development with Node.js ecosystem. So some problems are brought in Marp Core:
postcss-minify-paramsis depending onbrowserslist, is originally not need in Marp Core.postcss-minify-paramsis using__dirnameso brings incompatibillity with ESM. (Usage or marp-core in browser context #314)Cons: Prebundle will bring complex rollup setting. I have thought about porting plugin implementation from originals, but I thought prebundling is still better to keep up to the latest of (more complex) minify logics.
Fix #314.