npm / cn

cn

What changed in cn 0.2 to 0.5, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-18.

2 breaking3 new APIs and options7 performance4 behavior and defaults16 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

cn 0.54 changes

The build command drops names declared before a --*: initial reset.
0.5.0release notes
Node 20 is no longer supported; Node 22 or later is required.
0.5.0release notes

The build command reads @theme declarations that appear after nested blocks such as @keyframes.
0.5.0release notes

cn build and the plugins now register theme scales declared in Tailwind CSS.
0.4.0release notes

Adds a library entry point with build(options), letting build scripts and bundler plugins run scanning, subsetting, compiling, and writing directly.
0.3.0release notes
Adds the cn/next entry point.
0.3.0release notes
Adds the cn/vite entry point.
0.3.0release notes

Calls with an interpolated argument no longer thrash the argument cache, improving performance for that call shape; stable arguments are unchanged.
0.3.3release notes

Axis utilities now override the logical sides they cover, matching tailwind-merge 3.7.0. For example, px-2 replaces ps-* and pe-*.
0.3.1release notes

The generated .ts output typechecks with noUncheckedIndexedAccess and the rest of the @tsconfig/strictest flags; the .mjs output is unchanged.
0.3.3release notes
Custom animate-* classes are no longer merged, matching tailwind-merge; plugin classes such as animate-in, animate-once, and animate-duration-500 are never dropped.
0.3.2release notes

Object and array arguments resolve in place and use the argument-identity cache, avoiding a full clsx join on every call.
0.2.3release notes
A single array argument uses the argument path, allowing stable element identities to hit the cache.
0.2.3release notes
The argument-cache bucket now holds 256 tuples instead of 8, reducing evictions when many usage sites share a base string.
0.2.3release notes
Freshly joined strings pass through a doorkeeper before the whole-string cache, preventing arbitrary dynamic values from churning both caches.
0.2.3release notes
On JavaScriptCore, the whole-string cache uses a Map and an inlinable hit path, improving cache hits and recurring single-string calls on bun.
0.2.3release notes
Warm calls with four or more arguments now probe predictions in place and allocate nothing, reducing call time from about 44ns to 32ns.
0.2.1release notes

Config extensions accept readonly arrays, allowing token tuples declared with as const to work without a defensive copy.
0.2.5release notes

Fixes merging for containment.
0.2.6release notes
Fixes merging for custom animations.
0.2.6release notes
Fixes merging for legacy gradients.
0.2.6release notes
Fixes missing Tailwind v4 utilities in merging.
0.2.6release notes
The generated output file is excluded from content scans when its path matches a content glob.
0.2.5release notes
Extensions accept a single class or theme definition instead of throwing.
0.2.5release notes
Fixes brace globs, dot-directory and symlink scanning, and CLI error reporting for content builds.
0.2.4release notes
Fixes a hang and dropped classes when tracking conflicts with large custom configs and merges.
0.2.4release notes
Matches tailwind-merge on array-like values passed to twJoin.
0.2.4release notes
Matches tailwind-merge on Unicode whitespace.
0.2.4release notes
Fix the published types for cn/config, which pointed at an internal chunk with mangled export names and omitted defaultConfig and mergeConfigs.
0.2.2release notes
Fix the published type for clsx in cn/lite, which incorrectly accepted zero parameters.
0.2.2release notes
Fix conflict detection silently failing after 2^31 cache-missing merges in one process.
0.2.2release notes