
Security News
Crates.io Users Targeted by Phishing Emails
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
postcss-var-replace
Advanced tools
PostCSS plugin to replace CSS variables` with their static values.
This plugin provides a future-proof way of using most of CSS variables features, including selector cascading (with some caveats).
This package requires an LTS Node version (v18.0.0+)
npm add postcss-var-replace
For more general PostCSS usage, look here.
import postcss from 'postcss';
import { postcssVarReplace } from 'postcss-var-replace';
const input = `
:root {
--font-name: 'my-font-family-name';
}
@font-face {
font-family: var(--font-name);
src: url('myfont.woff2') format('woff2');
}`;
const { css } = postcss([postcssVarReplace()]).process(input);
console.log(css);
preserve
Type: boolean
Default: false
Allows you to preserve custom properties & var() usage in output.
Possible values:
false
: Removes --var
declarations and replaces var()
with their resolved/computed values.true
: Keeps var()
declarations in the output and has the computed value as a fallback declaration. Also keeps computed --var
declarations.'computed'
: Keeps computed --var
declarations in the output. Handy to make them available to your JavaScript.(declaration) => boolean|'computed'
: function/callback to programmatically return whether preserve the respective declarationpreserveAtRulesOrder
Type: boolean
Default: false
Keeps your at-rules like media queries in the order to defined them.
Ideally, this would be defaulted to true
and it will be in the next major version. All of the tests expecations need to be updated and probably just drop support for preserveAtRulesOrder: false
preserveInjectedVariables
Type: boolean
Default: true
Whether to preserve the custom property declarations inserted via the variables
option from final output.
A typical use case is CSS Modules, where you would want to avoid
repeating custom property definitions in every module passed through this plugin. Setting this option to false
prevents JS-injected variables from appearing in output CSS.
import postcss from 'postcss';
import { postcssVarReplace } from 'postcss-var-replace';
postcss([
postcssVarReplace({
variables: {
'--some-var': '100px',
'--other-var': {
value: '#00ff00'
},
'--important-var': {
value: '#ff0000',
isImportant: true
}
}
})
]).process(css, opts);
variables
Type: object
Default: {}
Define an object map of variables in JavaScript that will be declared at the :root
scope.
Can be a simple key-value pair or an object with a value
property and an optional isImportant
bool property.
The object keys are automatically prefixed with --
(according to CSS custom property syntax) if you do not provide it.
We 💛 contributions! After all, this is a community-driven project. We have no corporate sponsorship or backing. The maintainers and users keep this project going!
Please check out our Contribution Guide.
This is a modern fork of https://github.com/MadLittleMods/postcss-css-variables
FAQs
PostCSS plugin to replace CSS variables with their static values
The npm package postcss-var-replace receives a total of 12,866 weekly downloads. As such, postcss-var-replace popularity was classified as popular.
We found that postcss-var-replace demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.
Product
Socket now lets you customize pull request alert headers, helping security teams share clear guidance right in PRs to speed reviews and reduce back-and-forth.
Product
Socket's Rust support is moving to Beta: all users can scan Cargo projects and generate SBOMs, including Cargo.toml-only crates, with Rust-aware supply chain checks.