postcss-cssnext 3.1.1

Use tomorrow’s CSS syntax, today

postcss-cssnext@3.1.1 was published on 2021-09-13. Its manifest declares 31 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: 'postcss-cssnext' has been deprecated in favor of 'postcss-preset-env'. Read more at https://moox.io/blog/deprecating-cssnext/

All postcss-cssnext versions · Permanent reference to 3.1.1 · Latest release

Package specifications

Version3.1.1
License declarationMIT
Published2021-09-13T09:59:10.015Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count31
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size80.30 KiB
Published file count23
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies90
Repository stars5254
Repository forks183

Install postcss-cssnext 3.1.1

npm install postcss-cssnext@3.1.1
pnpm add postcss-cssnext@3.1.1
yarn add postcss-cssnext@3.1.1

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review2/10 — Found 8/27 approved changesets -- score normalized to 2
Maintained0/10 — project is archived
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy0/10 — security policy file not detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness