1. postcss-custom-media
Use Custom Media Queries in CSS
postcss-custom-media
Package: postcss-custom-media
Created by: csstools
Last modified: Wed, 13 Mar 2024 18:57:24 GMT
Version: 10.0.4
License: MIT
Downloads: 26,093,046
Repository: https://github.com/csstools/postcss-plugins

Install

npm install postcss-custom-media
yarn add postcss-custom-media

PostCSS Custom Media PostCSS Logo

npm version Build Status Discord

Baseline Status CSS Standard Status

 npm install postcss-custom-media --save-dev

PostCSS Custom Media lets you define @custom-media in CSS following the Custom Media Specification.

@custom-media --small-viewport (max-width: 30em);

@media (--small-viewport) {
	/* styles for small viewport */
}

/* becomes */

@media (max-width: 30em) {
	/* styles for small viewport */
}

true and false

With @custom-media you can use the constants true and false.
These are especially handy when debugging.

If you are unsure how your page is affected when a certain media query matches or not you can use these, to quickly toggle the results.
This plugin downgrades these queries to something that works in all browsers.

Quickly check the result as if the query matches:

@custom-media --small-viewport true;

@media (--small-viewport) {
	/* styles for small viewport */
}

/* becomes */

@media (max-color:2147477350) {
	/* styles for small viewport */
}

Quickly check the result as if the query does not match:

@custom-media --small-viewport false;

@media (--small-viewport) {
	/* styles for small viewport */
}

/* becomes */

@media (color:2147477350) {
	/* styles for small viewport */
}

logical evaluation of complex media queries

It is impossible to accurately and correctly resolve complex @custom-media queries
as these depend on the browser the queries will eventually run in.

Some of these queries will have only one possible outcome but we have to account for all possible queries in this plugin.

[!NOTE]
When handling complex media queries you will see that your CSS is doubled for each level of complexity.

GZIP works great to de-dupe this but having a lot of complex media queries will have a performance impact.

An example of a very complex (and artificial) use-case :


@custom-media --a-complex-query tty and (min-width: 300px);

@media not screen and ((not (--a-complex-query)) or (color)) {
	/* Your CSS */
}

/* becomes */


@media tty and (min-width: 300px) {
@media not screen and ((not (max-color:2147477350)) or (color)) {
	/* Your CSS */
}
}
@media not  tty and (min-width: 300px) {
@media not screen and ((not (color:2147477350)) or (color)) {
	/* Your CSS */
}
}

Usage

Add PostCSS Custom Media to your project:

 npm install postcss postcss-custom-media --save-dev

Use it as a PostCSS plugin:

 const postcss = require('postcss');
const postcssCustomMedia = require('postcss-custom-media');

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

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

Options

preserve

The preserve option determines whether the original notation
is preserved. By default, it is not preserved.

 postcssCustomMedia({ preserve: true })
@custom-media --small-viewport (max-width: 30em);

@media (--small-viewport) {
	/* styles for small viewport */
}

/* becomes */

@custom-media --small-viewport (max-width: 30em);

@media (max-width: 30em) {
	/* styles for small viewport */
}

@media (--small-viewport) {
	/* styles for small viewport */
}

Modular CSS Processing

If you're using Modular CSS such as, CSS Modules, postcss-loader or vanilla-extract to name a few, you'll probably
notice that custom media queries are not being resolved. This happens because each file is processed separately so
unless you import the custom media query definitions in each file, they won't be resolved.

To overcome this, we recommend using the PostCSS Global Data
plugin which allows you to pass a list of files that will be globally available. The plugin won't inject any extra code
in the output but will provide the context needed to resolve custom media queries.

For it to run it needs to be placed before the PostCSS Custom Media plugin.

 const postcss = require('postcss');
const postcssCustomMedia = require('postcss-custom-media');
const postcssGlobalData = require('@csstools/postcss-global-data');

postcss([
	postcssGlobalData({
		files: [
			'path/to/your/custom-media-queries.css'
		]
	}),
	postcssCustomMedia(/* pluginOptions */)
]).process(YOUR_CSS /*, processOptions */);

RELATED POST

10 Must-Know Windows Shortcuts That Will Save You Time

10 Must-Know Windows Shortcuts That Will Save You Time

Arrays vs Linked Lists: Which is Better for Memory Management in Data Structures?

Arrays vs Linked Lists: Which is Better for Memory Management in Data Structures?

Navigating AWS Networking: Essential Hacks for Smooth Operation

Navigating AWS Networking: Essential Hacks for Smooth Operation

Achieving Stunning Visuals with Unity's Global Illumination

Achieving Stunning Visuals with Unity's Global Illumination

Nim's Hidden Gems: Lesser-known Features for Writing Efficient Code

Nim's Hidden Gems: Lesser-known Features for Writing Efficient Code