chore(release): version packages - #10
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@e412/rnui-themes@0.3.0
Minor Changes
6108a93: Add a precompiled utility layer and a declared token export.
Why: rnui is normally consumed with Tailwind running in the consumer's build, so any class you write compiles on demand. But it is also consumed precompiled — as a single stylesheet embedded in a design tool or preview. In that mode a class Tailwind never emitted silently does nothing: no error, no warning, the element just renders unstyled. Ordinary layout markup (
gap-10,grid-cols-4,max-w-4xl,text-3xl) hit this constantly.@e412/rnui-themes/utilities— a precompiled stylesheet (~353 KB, ~40 KB gzip) covering complete scales rather than only the values rnui's own components happen to use:0–24acrossp m gap space-x space-y w h min-w min-hand every axis/side varianttext-xs–text-9xl,font-thin–font-black,tracking-*,leading-*grid-cols-1..12,col-span-*,row-span-*max-w-xs–max-w-7xl,rounded-*,border-*,opacity-0..100sm: md: lg: xl:responsive andhover: focus: active: disabled: dark:states on the interactive subsetImport it only if you cannot run Tailwind yourself; if you can, keep importing
@e412/rnui-themesand let your build compile what you use.@e412/rnui-themes/safelist— the safelist source, for adding these scales to your own Tailwind build.dist/utilities.json— the classes that actually shipped, derived from the compiled output rather than the safelist source, so tooling can tell a consumer "gap-9is not in this bundle" instead of letting it fail silently.dist/tokens.json— the declared public token surface: 399 tokens across every theme, each with its name, theme,kind(color|dimension|font|radius), value, and light/dark pair. Built from the hand-authored theme sources, never from compiled CSS, so Tailwind's internal custom properties are structurally excluded. This is now the source of truth for token extraction — do not scan the generated stylesheets. Tokens a theme's dark ramp omits are flaggeddarkInheritedrather than silently presented as declared.@e412/rnui-react: renamed the private custom properties--cell-size/--cell-radius(Calendar) and--data-grid-fill-size(DataGrid) to a--rnui-_prefix, so they are unambiguously internal and not mistaken for design tokens. These were never documented as customization points.--sidebar-widthand--sidebar-width-iconare deliberately unchanged: they are set via astyleprop onSidebarProvider, which is a supported override.@e412/rnui-react@0.3.0
Patch Changes
6108a93: Add a precompiled utility layer and a declared token export.
Why: rnui is normally consumed with Tailwind running in the consumer's build, so any class you write compiles on demand. But it is also consumed precompiled — as a single stylesheet embedded in a design tool or preview. In that mode a class Tailwind never emitted silently does nothing: no error, no warning, the element just renders unstyled. Ordinary layout markup (
gap-10,grid-cols-4,max-w-4xl,text-3xl) hit this constantly.@e412/rnui-themes/utilities— a precompiled stylesheet (~353 KB, ~40 KB gzip) covering complete scales rather than only the values rnui's own components happen to use:0–24acrossp m gap space-x space-y w h min-w min-hand every axis/side varianttext-xs–text-9xl,font-thin–font-black,tracking-*,leading-*grid-cols-1..12,col-span-*,row-span-*max-w-xs–max-w-7xl,rounded-*,border-*,opacity-0..100sm: md: lg: xl:responsive andhover: focus: active: disabled: dark:states on the interactive subsetImport it only if you cannot run Tailwind yourself; if you can, keep importing
@e412/rnui-themesand let your build compile what you use.@e412/rnui-themes/safelist— the safelist source, for adding these scales to your own Tailwind build.dist/utilities.json— the classes that actually shipped, derived from the compiled output rather than the safelist source, so tooling can tell a consumer "gap-9is not in this bundle" instead of letting it fail silently.dist/tokens.json— the declared public token surface: 399 tokens across every theme, each with its name, theme,kind(color|dimension|font|radius), value, and light/dark pair. Built from the hand-authored theme sources, never from compiled CSS, so Tailwind's internal custom properties are structurally excluded. This is now the source of truth for token extraction — do not scan the generated stylesheets. Tokens a theme's dark ramp omits are flaggeddarkInheritedrather than silently presented as declared.@e412/rnui-react: renamed the private custom properties--cell-size/--cell-radius(Calendar) and--data-grid-fill-size(DataGrid) to a--rnui-_prefix, so they are unambiguously internal and not mistaken for design tokens. These were never documented as customization points.--sidebar-widthand--sidebar-width-iconare deliberately unchanged: they are set via astyleprop onSidebarProvider, which is a supported override.Updated dependencies [6108a93]