css-codemod is a toolkit for running codemods over many CSS files to transform code, powered by PostCSS:
- Any PostCSS syntax parser and stringifier can be added. This extends support for additional syntaxes like SASS and LESS.
- Any PostCSS plugin can be added. This allows running any plugin as a one-off transform. This can be useful if you want to run a plugin once and remove it from a build tool or convert between syntaxes.
- Any PostCSS helpers for working with nodes and the abstract syntax tree can be used to transform CSS arbitrarily to fit your needs.
There are a few ways to use css-codemod.
First, using npx:
npx css-codemod "./src/**/*.css" -t ./transform.tsSecond, install and execute css-codemod with a package manager:
yarn add -D css-codemod
yarn css-codemod "./src/**/*.css" -t ./transform.tsThird, globally install css-codemod:
yarn add -g css-codemod
css-codemod "./src/**/*.css" -t ./transform.ts
The CLI provides the following options:
Usage:
$ css-codemod [files]
Commands:
[files] File path to transform. Note glob patterns are supported but must be wrapped in quotes.
For more info, run any command with the `--help` flag:
$ css-codemod --help
Options:
-t, --transform <transform> Path to the transform file (default: ./transform.ts)
-h, --help Display this message
-v, --version Display version number
Examples:
css-codemod ./a.css
css-codemod ./src/a.css
css-codemod "./src/**/*.css"
css-codemod "./**/*.css"This will pass the source of all files through the transform function specified with -t or --transform (defaults to ./transform.ts). See the following sections for more details on the transform function and API.
The transform function defines the transformation to make to each file. The transform can be written in either JavaScript or TypeScript, but TypeScript is recommended.
The transform function needs to be a named transform export from the transform file.
// transform.ts
// Import the `Transform` type to provide type-safety when
// using and creating a transform function.
import { Transform } from 'css-codemod';
// Define a named `transform` export function.
export const transform: Transform = (fileInfo, api) => {
// Implement the transform. See below for more details on the API.
};
// Optionally define a named `parser` export to configure the PostCSS parser.
// export const parser = ...;
// Optionally define a named `plugins` export to configure PostCSS plugins.
// export const plugins = [...];Define a transform function.
This type is provided to explicitly type the exported transform function. In general, this should be the only type that needs to be explicitly imported. The expected return value is either a string or null.
- When returned a string it will be written back to the original file. - When returned
null, nothing happens and the original file is skipped.
The first argument passed to the transform function.
It's an object with metadata about the current file being processed by the transform.
path: the resolved path of the file being transformed.source: the file contents source of the file being transformed.
The second argument passed to the transform function.
It's an object with helpers provided by css-codemod to perform transformations.
parse: parse a raw CSS string into an AST. This returns the root node of the underlying abstract syntax tree. Transformations can be made by making direct mutations to the underlying node. This is performed with PostCSS so the returned node is a PostCSS Root node. Refer to the PostCSS API documentation for documentation on nodes and various helpers.parseValue: parse a CSS string declaration value into a "mini" AST. This returns a result with all the nodes representing the string value. This is an alias for thepostcss-value-parserpackage. PostCSS itself doesn't parse values and working with complex string values can be challenging. Converting these string values into nodes when necessary can be useful. There are additional parsers for things like selectors, dimensions, media queries, etc. provided in the PostCSS documentation for plugins. If aliasing any of these would be useful open an issue (or pull request) with an example use case.
Define the PostCSS parser to use when parsing the CSS files. This is useful for adding support for additional syntaxes.
To configure, export parser with a PostCSS parser from the transform file.
Note: if you define a parser than you almost always want to pass the stringifier from the same package to root.toString(stringifier). This will guarantee the output is properly formatted using the same syntax.
Define PostCSS plugins to use when parsing the CSS files. This is useful for running plugins one-off, for example to upgrade syntax or perform other transformations already provided as plugins. Creating a custom plugin is one way that transform logic can be shared with other PostCSS tools and css-codemod. If you only want to share the codemod, then creating a transform file and sharing it is another option that requires less setup from others.
To configure, export plugins with an array of PostCSS plugins from the transform file.
// transform.ts
import { Transform } from 'css-codemod';
// Example PostCSS syntax extension. This isn't required.
import { parse, stringify } from 'postcss-scss';
// Example PostCSS plugin. This isn't required.
import calc from 'postcss-calc';
export const transform: Transform = (fileInfo, api) => {
// Convert the file source into an AST using the provided helper.
const root = api.parse(fileInfo.source);
// Use PostCSS helpers to walk through each descendant node
// Docs: https://postcss.org/api/#root-walk
root.walk(node => {
// Example logic to change all `color` declarations to have
// a value of red.
//
// For example:
// `color: green;` -> `color: red;`
// `color: #fff;` -> `color: red;`
// `color: rgb(0, 0, 0);` -> `color: red;`
if (node.type === 'decl' && node.prop === 'color') {
node.value = 'red';
}
});
// Convert the mutated AST back into a string.
// Since a string is returned this will be written back to the file.
//
// Note: in this example the `postcss-scss` package is used to add
// SCSS syntax support. The stringifier is passed when we call `toString` to
// re-output valid SCSS syntax.
return root.toString(stringify);
};
// Note: in this example the `postcss-scss` package is used to add SCSS syntax support.
// This configures PostCSS to correctly parse SCSS syntax.
// API docs: https://postcss.org/api/#parser
// Syntax docs: https://github.com/postcss/postcss/blob/main/docs/syntax.md
export const parser = parse;
// Note: in this example the `postcss-calc` package is used to compute `calc` expressions.
// This is used only as an example.
// API docs: https://postcss.org/api/#acceptedplugin
// Plugin docs: https://github.com/postcss/postcss/blob/main/docs/plugins.md
export const plugins = [calc({})];For more examples, see the codemod recipes.
PostCSS is the core tool used for performing code transformations. As a result, much of it's API is re-surfaced in this toolkit and will link to it's documentation.
AST Explorer is recommended when working on transforms. Change the language to "CSS" and the parser to "postcss" to see the underlying abstract syntax tree for a given snippet of CSS. This makes it much easier to understand the transformations that need to be made.
css-codemod is inspired by tools like jscodeshift to streamline CSS transformations whether it be an evolving codebase, or adopting newer syntax.
Read CSS codemods with PostCSS for a conceptual overview of how this toolkit works and the initial motivation.