ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #postcss
The objective is to verify that a minimal PostCSS configuration can trigger a parsing error such as “Unexpected token” before any plugin that depends on production credentials is executed. Key constraints include the lack of standardized plugin execution order across PostCSS versions and the default disabling of source maps, which may obscure error locations
Goal Ensure that every utility class needed at runtime appears in the production CSS even when class names are assembled dynamically, such as via string concatenation in JavaScript templates. Constraints Tailwind’s content scan only detects literal class names in configured files; dynamically built strings are ignored unless explicitly safelisted. Adding saf
Goal: decide whether to rely on postcss-preset-env as a single‑plugin solution or to compose the same transformations with individual plugins (e.g., postcss-custom-properties, autoprefixer, postcss-nesting) in order to eliminate duplicate transformations while still targeting the last two browser versions. Constraint: the build must preserve correct source‑m
On PostCSS 8, a plugin may return a Promise from its root handler or visitor hooks, and process() returns a LazyResult that settles only when every plugin finishes. The documented model covers completion and error propagation: it defines no abort signal, cancellation token, or per-plugin timeout. That leaves an open design question for anyone embedding PostC
PostCSS Async Plugin Execution Model PostCSS's plugin architecture supports both synchronous and asynchronous transformations through a standardized API where plugins receive the root AST node. The API allows plugins to return a promise for async operations, but the documentation does not clearly specify how promise resolution affects the execution order of
Context We are moving a build pipeline from PostCSS 7 to PostCSS 8 (assume 8.4.x). PostCSS 8 replaced the postcss.plugin() wrapper with factory objects exposing a postcssPlugin name, and made postcss a peer dependency so plugins share one instance. The uncertainty Our plugins array mixes older PostCSS 7-era packages with native PostCSS 8 plugins. The legacy
Goal is to use postcss-safe-parser to allow a CSS pipeline to continue when syntax errors appear during an upgrade. The documented capability is graceful degradation by rewriting the AST and removing or commenting malformed tokens. The uncertainty is how unknown at-rules are treated and whether the discardUnknown option controls that behavior consistently. V
tailwindcss