Product
Introducing Java Support in Socket
We're excited to announce that Socket now supports the Java programming language.
postcss-env-function
Advanced tools
The postcss-env-function package is a PostCSS plugin that allows you to use environment variables in your CSS. This can be particularly useful for setting values that may change depending on the environment, such as colors, sizes, or other design tokens.
Using environment variables in CSS
This feature allows you to define CSS variables that can be set using environment variables. The `env()` function takes the name of the environment variable and an optional fallback value.
/* CSS */
:root {
--main-bg-color: env(MAIN_BG_COLOR, #fff);
}
body {
background-color: var(--main-bg-color);
}
/* JavaScript to set environment variable */
process.env.MAIN_BG_COLOR = '#f0f0f0';
Fallback values
You can provide fallback values for environment variables in case they are not set. This ensures that your CSS will still have a valid value even if the environment variable is missing.
/* CSS */
:root {
--main-text-color: env(MAIN_TEXT_COLOR, #000);
}
p {
color: var(--main-text-color);
}
/* JavaScript to set environment variable */
process.env.MAIN_TEXT_COLOR = '#333';
The postcss-custom-properties package allows you to use CSS custom properties (variables) in a way that is compatible with older browsers. Unlike postcss-env-function, it does not directly support environment variables but focuses on transforming CSS custom properties to static values.
The postcss-preset-env package lets you convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. It includes features like custom properties, but does not specifically handle environment variables like postcss-env-function.
The postcss-simple-vars package allows you to use Sass-like variables in your CSS. It is simpler and more limited compared to postcss-env-function, as it does not support environment variables and focuses on static variable definitions.
PostCSS Environment Variables lets you use env()
variables in CSS, following the CSS Environment Variables specification.
⚠️ Custom Environment Variables were never defined in a specification and we are no longer including this in postcss-preset-env
.
In the future there might be renewed interest in Custom Environment Variables.
We advice users of this plugin to seek alternatives such as postcss-design-tokens
@media (max-width: env(--branding-small)) {
body {
padding: env(--branding-padding);
}
}
/* becomes */
@media (min-width: 600px) {
body {
padding: 20px;
}
}
/* when the `importFrom` option is: {
"environmentVariables": {
"--branding-small": "600px",
"--branding-padding": "20px"
}
} */
Add PostCSS Environment Variables to your project:
npm install postcss postcss-env-function --save-dev
Use it as a PostCSS plugin:
const postcss = require('postcss')
const postcssEnvFunction = require('postcss-env-function')
postcss([
postcssEnvFunction(/* pluginOptions */)
]).process(YOUR_CSS /*, processOptions */)
PostCSS Environment Variables runs in all Node environments, with special instructions for:
Node | PostCSS CLI | Webpack | Gulp | Grunt |
---|
The importFrom
option specifies sources where Environment Variables can be imported from, which might be JS and JSON files, functions, and directly passed objects.
postcssEnvFunction({
importFrom: 'path/to/file.js' /* module.exports = {
environmentVariables: {
'--branding-padding': '20px',
'--branding-small': '600px'
}
} */
})
@media (max-width: env(--branding-small)) {
body {
padding: env(--branding-padding);
}
}
/* becomes */
@media (min-width: 600px) {
body {
padding: 20px;
}
}
Multiple sources can be passed into this option, and they will be parsed in the order they are received. JavaScript files, JSON files, functions, and objects will need to namespace Custom Properties using the environmentVariables
or environment-variables
key.
postcssEnvFunction({
importFrom: [
/* Import from a CommonJS file:
module.exports = {
environmentVariables: {
'--branding-padding': '20px'
}
} */
'path/to/file.js',
/* Import from a JSON file:
{
"environment-variables": {
"--branding-padding": "20px"
}
} */
'and/then/this.json',
/* Import from an JavaScript Object: */
{
environmentVariables: { '--branding-padding': '20px' }
},
/* Import from a JavaScript Function: */
() => {
const environmentVariables = { '--branding-padding': '20px' }
return { environmentVariables }
}
]
})
See example imports written in JS and JSON.
Currently only valid custom property names (beginning with --
) are accepted.
Not all valid declaration value names are accepted.
Silence the deprecation notice that is printed to the console when using `importFrom``.
postcss-env-function is deprecated and will be removed. Check the discussion on github for more details. https://github.com/csstools/postcss-plugins/discussions/192
FAQs
Use env() variables in CSS
The npm package postcss-env-function receives a total of 4,136,912 weekly downloads. As such, postcss-env-function popularity was classified as popular.
We found that postcss-env-function demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers 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.
Product
We're excited to announce that Socket now supports the Java programming language.
Security News
Socket detected a malicious Python package impersonating a popular browser cookie library to steal passwords, screenshots, webcam images, and Discord tokens.
Security News
Deno 2.0 is now available with enhanced package management, full Node.js and npm compatibility, improved performance, and support for major JavaScript frameworks.