postcss-load-config automatically loads a PostCSS configuration and the PostCSS plugins defined in it, supporting multiple config formats such as package.json, .postcssrc, and postcss.config.js (including config files that export a function). It is useful when you want PostCSS to resolve the configured parser, source maps, and plugin list at build or runtime, without manually wiring them up.
Project status
- Maintenance status: Evidence of continued upstream activity exists (last upstream push on 2026-04-24), but the most recent published updates in the provided changelog stop at 6.0.1 on 2024-06-02, indicating a long release-update gap.
- Apparent update cadence: After 6.0.0 (2024-06-01) and 6.0.1 (2024-06-02), there are no further update summaries shown, so cadence appears quiet relative to today (2026-06-09), despite the later upstream push.
AI summary generated
Recent updates
6.0.1
Release 6.0.1 primarily claims a bug fix for bundlers support. The code changes are small (5 files) but include behavioral adjustments around how import failures for TypeScript loaders (tsx and jiti) are handled, plus a TypeScript compiler configuration change.
6.0.0
Version 6.0.0 changes how `.yaml` and `.yml` PostCSS configuration files are parsed by introducing a lazy, runtime import of the `yaml` package. The release notes provided by the publisher are missing, so the behavior change around YAML dependency availability is not clearly documented there.
Features5.1.0
Release 5.1.0 was published on 2024-05-01. No release notes were provided by the publisher, so the change set and any developer-impacting modifications are not documented in the available material.
v2.1.0
v2.1.0 adds synchronous configuration loading via postcssrc.sync. It also fixes plugin loading so that undefined plugin options are treated like no options. The code diff additionally changes configuration resolution behavior and default option handling beyond what the release notes describe.
Featuresv2.0.0
v2.0.0 is a major refactor of postcss-load-config, moving the implementation into src/, switching to cosmiconfig v4, and using import-cwd to resolve modules. It also reimplements option and plugin loading internally (src/options.js and src/plugins.js), with improved error messages that include the config file path.
BreakingFeaturesv1.2.0
v1.2.0 introduces support for loading PostCSS config files with extensions (for example, .postcssrc.json and .postcssrc.yaml). The code change enables this behavior by default via a default options merge, and the release also bumps several related dependencies.
Featuresv1.1.0
v1.1.0 adds the loaded configuration file path to the return value (config.file) and improves how errors are surfaced when PostCSS configuration cannot be found. The implementation also changes how NODE_ENV defaults and how input paths are normalized, and it bumps several runtime dependencies.
Featuresv1.0.0
This release is tagged v1.0.0, but no release notes were provided by the publisher. As a result, there is no documented information about new features, breaking changes, bug fixes, security updates, or migration steps.