Compiler provides a method for generating CSS according to given configuration from a given content and a method that can rewrite (mangle) selectors in a given content.


import { Compiler, nativePreset } from '@stylify/stylify';

const content = '<div class="color:blue"></div>';

const compiler = new Compiler(nativePreset.compiler);
const compilationResult = compiler.compile(content);

const css = compilationResult.generateCss();
// If the third parameter is set and if it is true (default) it rewrites selectors
// only in areas defined in selectorsAreas and not in whole content
const mangledContent = compiler.rewriteSelectors(content, compilationResult, true);


The configuration is different based on the tool and environment where the compiler is used. The example bellows shows configuration for Node.js and Browser. For more examples, checkout the integration examples page.


import { Compiler, nativePreset } from '@stylify/stylify';

// ---When adding config to native preset
// Example for macros and components when configuring native preset
nativePreset.compiler.variables = {
    blue: 'steelblue'
nativePreset.compiler.macros = {
    myMacro: ''
// ...

// --- When using custom config
const compiler = new Compiler({
    macros: {},
    variables: {},
    // ...

// --- You can also extend the configuration directly on instance
compiler.configure({ /* ... */})


    compiler: {
        // ...


In order to be as flexible as possible, Stylify provides a few useful features when writing selectors. Before you start using Stylify, you should check them first.

Selectors matching patern

Stylify takes a content and matches selectors using configured macros. Then it generates CSS from matched selectors. By default Stylify doesn't have any configuration and you have to configure it yourself.

Stylify does however provide the Native Preset . This preset provides a configuration containing useful helpers and a macro that matches 678 selector types from Chrome, Firefox, Opera, Edge and Safari.

The default pattern for all Stylify selectors is the following:

<screens and pseudo classes>:?<customSelector>

If you decide to use the Native Preset, the syntax is then extended to this:

<screens and pseudo classes>:?<property>:<value>

Screens and pseudo classes are optional. In case you need to use screen and pseudo class, the screen must be always before the pseudo class.



In case of writting a selector, that should contain a space, you can use __ (two underscores). These underscores are replaced by a space during compilation.

  • Spaces character: __ (two underscores)
border:1px__solid__red => border:1px solid red
width:calc(100%__-__8px) => width:calc(100% - 8px)


Some CSS properties requires quotes such as a font-family or a content. Because selectors are inside class attributes and therefore can be wrapped by a single quote or double quote, an alternative is necessary.

  • Quotes character: ^ (hat)
font-family:^Open__Sans^ => font-family:'Open Sans'
content:^Some__long__content^ => content:'Some long content'

Logical operands in screens

Screens can be randomly combined using logical operands. Before the CSS is generated, they are sorted in the following order:

asc - from smallest to largest, mobile first approach
desc - from largest to smallest, desktop first approach
  • without media query
  • min-width => asc
  • min-height => asc
  • max-width => desc
  • max-height => desc
  • min-device-width => asc
  • min-device-height => asc
  • max-device-width => desc
  • max-device-height => desc
  • light mode => according to above
  • dark mode => according to above
  • print => according to above
  • others

The sorting function can be changed (see configuration).

  • Logical AND: &&
  • Logical OR: ||


Compiler by default has no configuration. You can configure it using the options bellow.


If dev is set to true, the generated CSS will contain new lines and spaces to be more readable, selectors in generated CSS will not be mangled and if any variable is missing, only a warning will be shown in the console.

const compilerConfig = {
    dev: true


Macros are used to match selectors and generate css according to the match. The key inside the object can be a string or a regular expression.

Eeach matched selector is automatically mangled if enabled: color:rgb(255,255,255) => _abc123.

const compilerConfig = {
    macros: {
        'color:(\\S+?)': function (macroMatch, cssProperties): void {
            // color:blue => will create => color: blue
            // You can also use addMultiple({})
            cssProperties.add('color', macroMatch.getCapture(0));


<span class="color:red"></span>
<div class="color:#000"></span>
<div class="color:rgb(255,__255,__255)"></span>


Variables can be used in a selector or accessed inside a macro.

const compilerConfig = {
    variables: {
        blue: '#01befe',
        shadow: '0 8px 32px -8px rgb(0, 0, 0, 0.2)'
    // By default variables are replaced by their value. If this option is enabled, they
    // are replaced by var(--variableName) and can be more dynamic.
    // This is great for example for switching between light and dark mode.
    replaceVariablesByCssVariables: false,
    // By default, variables are automatically injected into the generated CSS as CSS variables.
    // You can change this behavior by setting the option bellow to false
    injectVariablesIntoCss: true


<span class="color:$blue"></span>


Screens are used to generate media queries. The key can be a string or a regular expression.

const compilerConfig = {
    screens: {
        'sm': '(min-width: 400px)',
        // Screens can also be functions
        // That allows you to make as flexible screen as possible
        'minw\\w+': (screen) => `(min-width: ${screen.replace('minw', '')})`


<span class="sm:color:darkred"></span>
<div class="minw640px:color:$blue"></span>
<div class="minw80rem:color:darkgreen"></span>


Components can decrease the amount of selectors in a template.

const compilerConfig = {
    components: {
        // selector => dependencies
        'button': 'padding:4px background:black color:white hover:background:grey',
        'container': `
        // You can define multiple components in one key, just separate them by "," (comma)
        'wrapper, footer': 'padding:24px',
        // When one component is defined multiple times, the selectors are merged
        // When selectorsChain is defined the last one is applied
        'wrapper': 'margin-top:24px',
        // When you are creating a component modifier you should add the selectorsChain
        // to increase the CSS specificity
        'button--big': {
            selectors: 'font-size:48px',
            selectorsChain: 'button'

Component can also be defined by calling the compiler addComponent method. This method expects configuration object as shown with the button--big component or a selectors string or an array of selectors strings:

const compiler = new Compiler(/* ... */);

compiler.addComponent('button', '...');


<span class="button"></span>
<div class="container"></div>


Plain selectors allows you to write CSS selectors for elements

const compilerConfig = {
    plainSelectors: {
        // selector => dependencies
        'article': 'font-size:16px line-height:28px color:#222',
        'article h1, article h2': 'color:blue',




In case you want to add for example a hover:color:blue to a selector, you should follow the approaches bellow. It is becuase when a pseudo class is used in a dependency, it is added on the end of the selector and that might not be alwas that what you want.

If the selector is indirect like div > button, article a, you should add the dependency like this:

const compilerConfig = {
    plainSelectors: {
        // First without the pseudo class
        'article a': 'color:green',
        // Then with the pseudo class
        'article a:hover': 'color:blue'
        'article a:hover i': 'color:white'

When the selector is direct like an a, input or a class like a.button, .link you can use the approch above and bellow:

const compilerConfig = {
    plainSelectors: {
        'a': 'color:green hover:color:blue',
        '': 'color:green hover:color:red'


Helpers are functions that can be called when a selector is matched and its properties are being generated.

Helpers can also be used directly in selectors. It is done automatically in the Native Preset. If you don't use this preset, you must configure it on your own using onNewMacroMatch hook. Example of such integration can be found in the native preset config .
const compilerConfig = {
    helpers: {
        shortcut(value) {
            const shortcuts = {
                'bgc': 'background-color',
                'zi': 'z-index'

            return value in shortcuts ? shortcuts[value] : value;
    macros: {
        '(bgc|zi):(\\S+?)': function (macroMatch, cssProperties) {
            const property = this.helpers.shortcut(macroMatch.getCapture(0));
            macroMatch.add(property, cssProperties.getCapture(1));


<div class="zi:2 bgc:red"></div>


In case you want to rewrite selectors in any framework specific class attribute, you must define that attribute to be matched. By default Stylify only rewrites class="" and class=''.

const compilerConfig = {
    selectorsAreas: [
        // Vue.js
        // React
        '(?:^|\\s+)className="([^"]+)"', '(?:^|\\s+)className=\\{`((?:.|\n)+?)`\\}',
        // Angular
        '(?:^|\\s+)[className]="([^"]+)"', '(?:^|\\s+)[ngClass]="{((?:.|\n)+?)}"',
        // Nette framework
        // ...


stylify-ignore and stylify-runtime-ignore are by default areas you can use to remove content from compilation.

Then there are the following tags, that are ignored (only without attributes): `code, head, pre, script, style.

Ignored tags can be configured but they are always matched without attributes because no html parser is integrated in Stylify and is not reliable to match them with regular expressions. The ignoredElements options is marked as @internal to keep you away from this option.
const compilerConfig = {
    ignoredAreas: [

stylify-ignore (and any other ignore element) can be placed inside a comment and therefore can be used in any file format.

<!-- stylify-ignore -->
Everything between these tags will be ignored
<div class="color:red"></div>
<!-- /stylify-ignore -->


The pregenerate option allows you to add some content into the compilation process.

const compilerConfig = {
    pregenerate: 'color:red color:blue width:100%'


Some configuration can be only a file or bundle specific. Because of that Stylify provides a content options that are processed during a compilation and provides a way to define a components, variables and etc. only for a specific file or bundle.

Common syntax is the following:

stylify-<option> /stylify-<option>

The default available content options are listed bellow:

// Components expects a valid javascript object as value
    button: `font-size:24px padding:4px`,
    'button--big': {
        selectors: 'font-size:48px',
        selectorsChain: 'button'

// Variables expects a valid javascript object as value
    blue: `#01befe`

// Plain selectors expects a valid javascript object as value
    article: `font-size:24px`

// Pregenerate expects a string

    'testScreen': '(min-width: 123px)',
    'dynamic\\w+': (screen) => `(max-width: ${screen.replace('dynamic', '')})`

It is possible to define own content options processor:

An example of a content option definition can be found inside the @stylify/bundler package .
const compilerConfig = {
    contentOptionsProcessors: {
        // Content options is an object of already matched options.
        // OptionMatch value is the matched value of your option
        // stylify-myOption optionMatchValue /stylify-myOption
        myOption: (contentOptions, optionMatchValue) => {
            // Process the option value ...

            contentOptions.myOptionData = optionMatchValue;
            // You must return the contentOptions object
            return contentOptions;


In the Compiler there are two hooks that you can use to streamline or extend the Stylify functionality.


This hook is called when the compile function is called and the new CompilationResult is created or updated. You can for example change the configuration of the compilation result or see what is happening under the hood.

An example of this hook usage can be found on the @stylify/autoprefixer page.
const compilerConfig = {
    onPrepareCompilationResult: (compilationResult) {


When a selector is matched by macro within a content a new MacroMatch is created. Right after its creation this hook is called with the MacroMatch as its argument.

The selector properties inside the hook already contains values of variables if they vere in the selector.

An example of this hooks usage can be found in the Native Preset code .
const compilerConfig = {
    onNewMacroMatch: (macroMatch, selectorProperties) {

Compilation Result

Compilation result can be created or configured and passed into the Compiler as a second argument. By this approach, you can change the compilation behavior and extend the functionality.

Be aware that if you modifie compilation result or create a new one with a wrong configuration, you can break the whole compilation process.
An example of CompilationResult hooks usage can be found on the @stylify/autoprefixer page.
const compilationResult = new CompilationResult({
    // All options are optional
    dev: false,
    // If reconfigurable is set to false, the configuration will not change
    reconfigurable: false,
    // This function is responsible for sorting screens before the CSS is generated.
    // The argument is a Map type and the function must also return a Map type.
    screensSortingFunction: (screensList) => { return screensList },
    // If mangle selectors is true, selectors within the CSS will be manhled
    mangleSelectors: false,
    // A hook, that is called when a new CssRecord is created
    onPrepareCssRecord: (cssRecord) => { console.log(cssRecord) }

CSS Record

Css record can be accessed only through a hook from compilation result.

An example of CssRecord hooks usage can be found on the @stylify/autoprefixer page.
const compilationResult = new CompilationResult({
    onPrepareCssRecord: (cssRecord) => {
        // This hook passes property and a its value as arguments.
        // The function must return an null, nothing or an object its structure is the following
        // { property: value, anotherProperty: value}
        cssRecord.onAddProperty = (property, value) => {
            console.log(property, value);

            // Return is optional
            return { [property]: value };
        // This hook receives actual cssRecord as argument
        cssRecord.onAfterGenerate = (cssRecord) => {