@csstools/postcss-progressive-custom-properties

v4.0.0

Correctly declare progressive enhancements for CSS Custom Properties. For more information about how to use this package see README

Latest version published 4 months ago

License: MIT-0

NPM

GitHub

Package Health Score

98 / 100

security
No known security issues
popularity
Influential project
maintenance
Healthy
community
Active

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
4.0.0	\|	08/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.3.0	\|	07/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.3.0	\|	06/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.3.0	\|	03/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.2.0	\|	02/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT-0

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (4,024,666)

GitHub Stars: 908
Forks: 73
Contributors: 130

Direct Usage Popularity

The npm package @csstools/postcss-progressive-custom-properties receives a total of 4,024,666 downloads a week. As such, we scored @csstools/postcss-progressive-custom-properties popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @csstools/postcss-progressive-custom-properties, we found that it has been starred 908 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 130
Funding: Yes

A good and healthy external contribution signal for @csstools/postcss-progressive-custom-properties project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 5
Open PR: 2
Last Release: 4 months ago
Last Commit: 2 days ago

Further analysis of the maintenance status of @csstools/postcss-progressive-custom-properties based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @csstools/postcss-progressive-custom-properties demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=18

Age: 3 years
Dependencies: 1 Direct
Versions: 20
Install Size: 50.4 kB
Dist-tags: 1
# of Files: 7
Maintainers: 3
TS Typings: No

@csstools/postcss-progressive-custom-properties has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

PostCSS Progressive Custom Properties

PostCSS Progressive Custom Properties is a utility plugin to correctly declare Custom Property fallbacks and enhancements.

> [!WARNING] > It is not intended to be used directly by stylesheet authors. > Meant to be included in other PostCSS plugins that provide CSS value transforms as fallbacks.

Custom Properties are not discarded like regular declarations when invalid. This makes it tricky to provide fallback values for older browsers.

The solution is to wrap Custom Property declarations in an @supports rule.

:root {
	/* fallback */
	--a-color: red;
	/* progressive enhancement */
	--a-color: oklch(40% 0.234 0.39 / var(--opacity-50));
}

/* becomes */

:root {
	--a-color: red;
}

@supports (color: oklch(0% 0 0)) {
	:root {
		--a-color: oklch(40% 0.234 0.39 / var(--opacity-50));
	}
}

Ignored values

initial and `` are ignored.

.initial {
	--prop-1: red;
	--prop-1: initial;
}

.white-space {
	--prop-1: red;
	--prop-1:;

	--prop-2: red;
	--prop-2: ;

	--prop-3: red;
	--prop-3:    ;
}

/* remains */

.initial {
	--prop-1: red;
	--prop-1: initial;
}

.white-space {
	--prop-1: red;
	--prop-1:;

	--prop-2: red;
	--prop-2: ;

	--prop-3: red;
	--prop-3:    ;
}

Usage

Add PostCSS Progressive Custom Properties to your project:

npm install @csstools/postcss-progressive-custom-properties --save-dev

Use PostCSS Progressive Custom Properties as a PostCSS plugin:

const postcss = require('postcss');
const postcssCustomProperties = require('@csstools/postcss-progressive-custom-properties');

postcss([
  postcssProgressiveCustomProperties()
]).process(YOUR_CSS /*, processOptions */);

@supports

This plugin wraps Custom Property override declarations in an @supports rule. With PostCSS 8 this trigger declaration visitors to run again.

Make sure your plugin detects and ignores values inside relevant @supports rules.

Reading list

https://moderncss.dev/how-custom-property-values-are-computed/

PostCSS Progressive Custom Properties runs in all Node environments, with special instructions for:

Node	PostCSS CLI	Webpack	Gulp	Grunt

@csstools/postcss-progressive-custom-properties dependencies

postcss-value-parser

FAQs

What is @csstools/postcss-progressive-custom-properties?

Correctly declare progressive enhancements for CSS Custom Properties. Visit Snyk Advisor to see a full health score report for @csstools/postcss-progressive-custom-properties, including popularity, security, maintenance & community analysis.

Is @csstools/postcss-progressive-custom-properties popular?

The npm package @csstools/postcss-progressive-custom-properties receives a total of 4,024,666 weekly downloads. As such, @csstools/postcss-progressive-custom-properties popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @csstools/postcss-progressive-custom-properties well maintained?

We found that @csstools/postcss-progressive-custom-properties demonstrated a healthy version release cadence and project activity. It has a community of 130 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @csstools/postcss-progressive-custom-properties safe to use?

The npm package @csstools/postcss-progressive-custom-properties was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 21 November-2024, at 07:56 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP