Enhancement/issue 426 restore postcss as plugins #473
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
thescientist13
added
enhancement
thescientist13
changed the title
7 tasks
…sourceInterfact.intercept signature to include request and response headers
thescientist13
force-pushed
the
enhancement/issue-426-restore-babel-postcss-as-plugins
branch
from
2e285c0 to
13b8084
Compare
thescientist13
deleted the
enhancement/issue-426-restore-babel-postcss-as-plugins
branch
5 tasks
thescientist13
added a commit
that referenced
this pull request
Apr 3, 2021
* refactor postcss and import css to standalone plugins and refactor ResourceInterfact.intercept signature to include request and response headers * rollup and css plugin optimization compatibility * move cli postcss test to postcss plugin specs * more refactoring and refining * new rollup plugin API * postcss optimizations working and prism.css working again * got script file output working and comment cleanup * fix postcss config lookup * sort import order * remove commented out code * bundle and link CSS within the CLI and rollup by default * default css optimizations * specs for plugin-import-css * update docs and deleted outdated build docs
thescientist13
added a commit
that referenced
this pull request
Apr 3, 2021
* refactor postcss and import css to standalone plugins and refactor ResourceInterfact.intercept signature to include request and response headers * rollup and css plugin optimization compatibility * move cli postcss test to postcss plugin specs * more refactoring and refining * new rollup plugin API * postcss optimizations working and prism.css working again * got script file output working and comment cleanup * fix postcss config lookup * sort import order * remove commented out code * bundle and link CSS within the CLI and rollup by default * default css optimizations * specs for plugin-import-css * update docs and deleted outdated build docs
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.
Related Issue
part of #426
Summary of Changes
This a bit of doozy so here goes....
import someCss from './some.css';syntaxResourceInterface.optimization- not really for "bundling", if you need to get involved with bundling / rollup, create / drop in a a rollup pluginResourceInterface.serveandResourceInterface.interceptnow get both request and response headersTODOs
@importrules (as part of Rolluploadlifecycle?)Babel / Browserslist + preset-env(will make as new PR)Move HTML optimizations from- it can waitserlializelifecycle to rollup?Thoughts / Topics for Discussion
optimizationfeatures like terser or cssnano, then it might stand to reason we create a newoptimizationconfiguration called'none', so you can choose to disable itterserandjsonplugins outside of Rollup config, include via rollup pluginexports are starting to look really good right now... :)