@stylexswc/unplugin

Unplugin with NAPI-RS StyleX compiler integration

Part of the StyleX SWC Plugin workspace

Unplugin for an unofficial napi-rs compiler that includes the StyleX SWC code transformation under the hood.

Installation

To install the package, run the following command:

npm install --save-dev @stylexswc/unplugin

Usage

To use the plugin, you need to add it to your build tool configuration.

For every plugin have an example of how to use it in apps/{pluginName}-unplugin-example folder.

Plugins

Vite

// vite.config.ts
import StylexRsPlugin from '@stylexswc/unplugin/vite';

export default defineConfig({
  plugins: [
    StylexRsPlugin({
      /* options */
    }),
  ],
});

Rollup

// rollup.config.js
import StylexRsPlugin from '@stylexswc/unplugin/rollup';

export default {
  plugins: [
    StylexRsPlugin({
      /* options */
    }),
  ],
};

Webpack

// webpack.config.js
module.exports = {
  /* ... */
  plugins: [
    require('@stylexswc/unplugin/webpack')({
      /* options */
    }),
  ],
};

Rspack

// rspack.config.js
module.exports = {
  /* ... */
  plugins: [
    require('@stylexswc/unplugin/rspack')({
      /* options */
    }),
  ],
};

Nuxt

// nuxt.config.js
export default defineNuxtConfig({
  modules: [
    [
      '@stylexswc/unplugin/nuxt',
      {
        /* options */
      },
    ],
  ],
});

This module works for both Nuxt 2 and Nuxt Vite

Vue CLI

// vue.config.js
module.exports = {
  configureWebpack: {
    plugins: [
      require('@stylexswc/unplugin/webpack')({
        /* options */
      }),
    ],
  },
};

esbuild

// esbuild.config.js
import { build } from 'esbuild';
import StylexRsPlugin from '@stylexswc/unplugin/esbuild';

build({
  plugins: [StylexRsPlugin()],
});

Plugin Options

Basic Options

rsOptions

• Type: Partial<StyleXOptions>
• Optional
• Description: StyleX compiler options that will be passed to the NAPI-RS compiler. For standard StyleX options, see the official StyleX documentation.

[!NOTE] New Features: The include and exclude options are exclusive to this NAPI-RS compiler implementation and are not available in the official StyleX Babel plugin.

rsOptions.include

• Type: (string | RegExp)[]
• Optional
• Description: RS-compiler Only An array of glob patterns or regular expressions to include specific files for StyleX transformation. When specified, only files matching at least one of these patterns will be transformed. Patterns are matched against paths relative to the current working directory.

rsOptions.exclude

• Type: (string | RegExp)[]
• Optional
• Description: RS-compiler Only An array of glob patterns or regular expressions to exclude specific files from StyleX transformation. Files matching any of these patterns will not be transformed, even if they match an include pattern. Patterns are matched against paths relative to the current working directory.

fileName

• Type: string
• Default: 'stylex.css'
• Description: Name of the generated CSS file.

useCSSLayers

• Type: UseLayersType
• Default: false
• Description: Enables CSS cascade layers support for better style isolation.

extractCSS

• Type: boolean
• Default: true
• Description: Controls whether CSS should be extracted into a separate file.

pageExtensions

• Type: string[]
• Default: ['js', 'jsx', 'ts', 'tsx', 'mjs', 'mts']
• Description: File extensions to process for StyleX transformations.

useCssPlaceholder

• Type: boolean | string
• Default: false
• Description: Enable CSS injection into CSS files via placeholder marker.
  • When set to true, the plugin will look for the default @stylex; marker
  • When set to a string, the plugin will use that string as the custom marker

Benefits

• CSS Processing: Generated StyleX CSS goes through the bundler's CSS pipeline (PostCSS, LightningCSS, css-loader, etc.)
• Deterministic Builds: No race conditions or hash instability from virtual modules
• Consistent Output: All CSS follows the same processing rules and bundling strategy
• Build Optimization: CSS can be code-split and optimized alongside other stylesheets
• Works Everywhere: Same approach works for Vite, Webpack, Rspack, esbuild, Rollup, and Farm

How to Use

• Create a CSS file with a marker (e.g., global.css):

/* global.css */
:root {
  --brand-color: #663399;
}

body {
  margin: 0;
  font-family: system-ui, sans-serif;
}

@stylex;

• Import the CSS file in your entry point:

// src/main.ts
import './global.css';
import { App } from './App';

• Configure the plugin with useCssPlaceholder:

// vite.config.ts (or webpack.config.js, rspack.config.js, etc.)
import StylexRsPlugin from '@stylexswc/unplugin/vite';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    StylexRsPlugin({
      useCssPlaceholder: true, // Uses default '@stylex;' marker
      useCSSLayers: true,
    }),
  ],
});

Using a Custom Marker

You can specify a custom marker string:

/* global.css */
:root {
  --brand-color: #663399;
}

/* INJECT_STYLEX_HERE */

StylexRsPlugin({
  useCssPlaceholder: '/* INJECT_STYLEX_HERE */',
  useCSSLayers: true,
})

The plugin will replace the marker with the generated StyleX CSS during the build process.

[!NOTE] When useCssPlaceholder is enabled, the plugin will no longer inject CSS automatically into HTML or emit a separate stylex.css file. The CSS is injected into your specified CSS file.

[!IMPORTANT] Migration from useViteCssPipeline

The useViteCssPipeline option (which used virtual CSS modules) has been replaced with the useCssPlaceholder approach. The new approach uses real CSS files instead of virtual modules, which provides:

• Better compatibility across all bundlers
• No race conditions or timing issues
• Deterministic builds with stable hashes

To migrate, simply create a CSS file with a marker and set useCssPlaceholder: true (or use a custom marker string).

Example Configuration

// vite.config.ts
import StylexRsPlugin from '@stylexswc/unplugin/vite';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    StylexRsPlugin({
      rsOptions: {
        dev: process.env.NODE_ENV !== 'production',
        // Include only specific directories
        include: ['src/**/*.{ts,tsx}', 'components/**/*.{ts,tsx}'],
        // Exclude test files and stories
        exclude: ['**/*.test.*', '**/*.stories.*', '**/__tests__/**'],
      },
      useCSSLayers: true,
      useCssPlaceholder: true,
    }),
  ],
});

Path Filtering Examples

Include only specific directories:

StylexRsPlugin({
  rsOptions: {
    include: ['src/**/*.tsx', 'app/**/*.tsx'],
  },
})

Exclude test and build files:

StylexRsPlugin({
  rsOptions: {
    exclude: ['**/*.test.*', '**/*.spec.*', '**/dist/**', '**/node_modules/**'],
  },
})

Using RegExp with lookahead/lookbehind - exclude node_modules except specific packages:

StylexRsPlugin({
  rsOptions: {
    // Exclude all node_modules except @stylexjs packages
    exclude: [/node_modules(?!\/@stylexjs)/],
  },
})

Transform only specific packages from node_modules:

StylexRsPlugin({
  rsOptions: {
    include: [
      'src/**/*.{ts,tsx}',
      'node_modules/@stylexjs/open-props/**/*.js',
      'node_modules/@my-org/design-system/**/*.js',
    ],
    exclude: ['**/*.test.*'],
  },
})

Using regular expressions:

StylexRsPlugin({
  rsOptions: {
    include: [/src\/.*\.tsx$/],
    exclude: [/\.test\./, /\.stories\./],
  },
})

Combined include and exclude (exclude takes precedence):

StylexRsPlugin({
  rsOptions: {
    include: ['src/**/*.{ts,tsx}'],
    exclude: ['**/__tests__/**', '**/__mocks__/**'],
  },
})

License

MIT — see LICENSE