Registry / web-framework / lightningcss-win32-arm64-msvc

lightningcss-win32-arm64-msvc

library1.32.0jsnpmunverified

LightningCSS is a high-performance CSS parser, transformer, and minifier written in Rust, primarily developed by the Parcel Bundler team. It offers incredibly fast processing of CSS, including features like CSS Modules, nesting, vendor prefixing, and transpilation of modern CSS syntax down to older targets based on `browserslist`. The current stable version is 1.32.0, with frequent minor and patch releases, typically several times a month, reflecting active development and continuous alignment with the latest CSS specifications. Its key differentiators include its Rust-native performance, comprehensive CSS feature support, and its role as a core component in optimizing CSS delivery in modern web development workflows. This specific package (`lightningcss-win32-arm64-msvc`) provides the native binary for Windows ARM64 environments, which is dynamically loaded by the main `lightningcss` JavaScript package to enable native speed operations.

web-framework devops

npm install lightningcss-win32-arm64-msvc

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · LIGHTNINGCSS-WIN32

lightningcss-win32-arm64-msvc

web-frameworkjavascriptv1.32.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

transform

✓ import { transform } from 'lightningcss'

✗ const { transform } = require('lightningcss')

The `transform` function is the primary entry point for parsing, minifying, and transforming CSS. For CJS, it's `const { transform } = require('lightningcss');`

bundle

✓ import { bundle } from 'lightningcss'

✗ const { bundle } = require('lightningcss')

Use `bundle` for handling `@import` rules, which resolves and inlines external CSS dependencies into a single output file. It accepts options for custom resolvers.

browserslistToTargets

✓ import { browserslistToTargets } from 'lightningcss'

This utility function converts a `browserslist` query array into the format expected by `lightningcss` for target browser environments.

Demonstrates how to use `lightningcss` to parse, transform, and minify CSS, including setting browser targets.

import { transform, bundle, browserslistToTargets } from 'lightningcss'; import browserslist from 'browserslist'; const targets = browserslistToTargets(browserslist('>= 0.2% and not dead')); const inputCss = ` :root { --my-color: #f00; } @media (min-width: 768px) { .container { display: grid; gap: 1rem; color: var(--my-color); } } @import url('./variables.css'); `; // Example of transforming and minifying CSS const { code: transformedCode, map: sourceMap } = transform({ filename: 'input.css', code: Buffer.from(inputCss), minify: true, targets, sourceMap: true, }); console.log('Transformed & Minified CSS:\n', transformedCode.toString()); // Example of bundling CSS (requires actual files to resolve imports) // For a real-world scenario, ensure 'variables.css' exists. // const { code: bundledCode } = await bundle({ // filename: 'index.css', // baseURL: import.meta.url, // targets, // resolver: { // resolve(specifier, from) { // // Basic resolver for demonstration // if (specifier === './variables.css') { // return new URL('./variables.css', from); // } // return null; // } // }, // // code: Buffer.from(inputCss) // Only for direct code input without file resolution // }); // console.log('Bundled CSS:\n', bundledCode.toString());

Debug

Known issues

breakingThe relative color parsing implementation was updated to align with the latest CSS specification. This change affects how percentages and `calc()` expressions are handled within relative color calculations, potentially requiring updates to existing stylesheets that rely on previous interpretations.

fix

Review CSS code utilizing relative color syntax. Where percentages were previously used, evaluate if numbers are now required according to the updated spec. Ensure `calc()` within colors strictly evaluates to numbers.

affects: >=1.30.0

gotchaAs a native module, `lightningcss` relies on platform-specific binaries. If the correct binary for your environment (OS, architecture, Node.js version) cannot be found or loaded, installation or runtime errors will occur. This specific package `lightningcss-win32-arm64-msvc` is for Windows ARM64 with MSVC toolchain.

fix

Ensure you are using a supported Node.js version (>=12.0.0). If encountering issues, try reinstalling `lightningcss` to force detection and installation of the correct native binding, or explicitly install the correct `@lightningcss/lightningcss-win32-arm64-msvc` if the automatic detection fails.

affects: >=1.0.0

gotchaIn v1.32.0, custom resolvers gained the ability to mark `@import` rules as external. If not handled correctly, this can lead to unbundled `@import` statements in the final CSS output when bundling, potentially breaking styles or increasing requests.

fix

When implementing custom resolvers for `bundle`, explicitly return `{ external: string }` if an `@import` should remain in the output without being bundled, or ensure all intended imports are resolved and inlined.

affects: >=1.32.0

Errors

Common errors & fixes

Error: Cannot find module '@parcel/css-win32-arm64-msvc' (or similar platform-specific binding)

The main `lightningcss` package could not find or load the appropriate native binary for your operating system and architecture. This often happens if an optional dependency fails to install, or if the environment doesn't match a pre-built binary.

fix

Ensure your Node.js version is compatible (>=12.0.0). Try deleting `node_modules` and `package-lock.json` then reinstalling `lightningcss`. If using a unique environment, you might need to compile from source or verify a pre-built binary exists for your specific platform.

Error: Invalid CSS at line X: Unexpected token

This error indicates that the input CSS contains syntax errors or features not yet supported by the version of LightningCSS being used, or that the input is malformed.

fix

Review the specified line and surrounding CSS for syntax errors. If using bleeding-edge CSS features, ensure your LightningCSS version is up to date. You can also temporarily disable minification or specific transformations to pinpoint the problematic area.

Upgrade

Version history

1.32.0latest on npm

Audit

Dependencies

lightningcssrequiredThis package is a platform-specific native binding for the main `lightningcss` JavaScript package. Users typically install `lightningcss`, which then manages the installation and loading of the appropriate native binary for their environment.

Agent activity

22 hits · last 30 days

node

Resources

githubhttps://github.com/parcel-bundler/lightningcss ↗

packagehttps://www.npmjs.com/package/lightningcss-win32-arm64-msvc ↗

homepagehttps://lightningcss.dev ↗