v0.3.0
Minor Changes
-
a7bf591: Add an
xl(2.5rem) size toIcon.Breaking for EmptyState icons:
EmptyStateno longer resizes the SVG you pass asicon. Pass<Icon size="xl" />to keep the previous 2.5rem size.
A hand-authored, stroke-based SVG icon set behind a single `Icon` component — the same idea as `@ant-design/icons`/`@mui/icons-material`, but self-contained (no new dependency). Icons use `stroke="currentColor"`, so they inherit color from whatever text color is in scope.
Set GITHUB_PACKAGES_TOKEN to list published versions. The repo is at v0.3.0.
a7bf591: Add an xl (2.5rem) size to Icon.
Breaking for EmptyState icons: EmptyState no longer resizes the SVG you pass as icon. Pass <Icon size="xl" /> to keep the previous 2.5rem size.
rectangle icon — a flat shape primitive that pairs with ellipse, matching its bounds so the two read as a set in a shape toolbar. The existing box icon remains the 3D carton glyph.f8c57db: Generate TypeScript declarations once per build instead of once per format.
dist/index.d.cts is no longer emitted. Nothing referenced it: each package's exports["."].types points at dist/index.d.ts, which is unchanged and still covers both the import and require conditions. There are no API, type, or runtime changes.
b98ff2a: republish with a valid stylesheet
0.2.1 shipped a dist/index.css ending in a stray ; and an unmatched },
which strict CSS parsers reject outright — it failed next build under
Turbopack rather than warning. The JS output was fine, so nothing caught it
before release.
The cause was a build race, not anything in icon.module.scss: tsup built the
cjs and esm formats concurrently and both esbuild passes wrote the same
dist/index.css. The shorter output landed over the longer one and the tail of
the longer survived. It reproduced on roughly a third of clean builds, which is
why only this package was hit in that release and why the surviving banner
comment differed between 0.2.0 and 0.2.1 — that was the winning writer, not
a plugin upgrade.
The shared component build config now runs the formats sequentially, so one
writer owns the stylesheet at a time. Consumers pinning 0.2.0 to dodge the
broken build can move back to the caret range.