PostCSS
summary
PostCSS claims let teams use future CSS today by wiring small plugins into a build: examples include postcss-nested for nesting, cssnext for custom properties and var/calc support, and cssnano for minification; AutoPrefixer already runs on PostCSS. It runs in Gulp, parses CSS into a tree, plugins transform and stringify, and the ecosystem shows ~500k npm downloads/week. Migration from SASS is largely a search‑and‑replace (mixins and filename tweaks), plugins are simple JS functions, performance beats Ruby implementations, but plugin ordering and excessive custom plugins can create maintenance friction.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:35PostCSS WHY?
- 7:00How does it work?
- 7:21Execution
- 10:57CSSNano
- 11:39Easy transition
- 11:57From SCSS to PostCSS
- 15:49Extend - new plugin
- 16:30Example: postcss-focus
- 18:33handle with care
- 23:18CSS is not a programming language
- 24:20LINKS
