astralkit 0.3.1 → 0.3.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,37 +1,49 @@
1
- # Changelog
2
-
3
- All notable changes to the `astralkit` SDK package.
4
-
5
- The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
- and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
-
8
- ## [0.3.1] — 2026-04-18
9
-
10
- ### Added
11
- - `peerDependencies` declaration: `tailwindcss >= 3.0.0`. Installing `astralkit` in a project without Tailwind now surfaces a clear peer-dep warning instead of silent breakage.
12
- - File header comment on `astralkit-theme.css` explicitly marks it as the Tailwind v3 legacy file. Points readers at the `astralkit/theme-v3` export path and explains the v4 alternative.
13
-
14
- ### Fixed
15
- - No functional changes from `0.3.0` this is a metadata + documentation patch.
16
-
17
- ## [0.3.0]2026-04-18
18
-
19
- ### Changed (breaking behavior fix)
20
- - **`astralkit/theme` export now resolves to the Tailwind v4 file (`astralkit-theme-v4.css`).** Previously it pointed at `astralkit-theme.css` (the v3 `:root {}` file), which meant Tailwind v4 users were loading tokens that weren't registered with Tailwind's `@theme` system. Utilities like `bg-ak-primary` and `text-ak-text` were only working because the separate `astralkit-utilities.css` contains its own `@theme` blocks; the theme import was effectively dead weight.
21
- - If you were relying on `@import "astralkit/theme"` resolving to the v3 `:root` syntax (e.g., in a Tailwind v3 project), import `astralkit/theme-v3` explicitly instead.
22
- - If you're on Tailwind v4, no action needed the new default is what you should have been getting all along.
23
-
24
- ### Added
25
- - New `astralkit/theme-v3` export — explicit path to the Tailwind v3 legacy file (`astralkit-theme.css`).
26
- - `astralkit/theme-v4` export retained (unchanged) — still points at the v4 file. Existing imports keep working.
27
- - v4 theme refinements across 12 commits of token architecture work (including rail/panel elevated color overrides, sidebar token tuning, avatar size/badge tokens, and Phase A token standardization).
28
- - `primitives/.npmignore` excludes `*.backup` and `*.pre-v4-split` scratch files from published tarballs. The `0.3.0` release removed ~220 kB of v3-migration scratch that was accidentally shipping in earlier versions.
29
-
30
- ### Fixed
31
- - Tailwind v3 plugin registration (via CLI init) now covers additional `plugins: [...]` formatting variants.
32
-
33
- ## [0.2.0] — 2026-04-02
34
-
35
- ### Added
36
- - Initial public release on npm.
37
- - Design tokens (theme CSS), utilities CSS, palette presets, primitives folder, `cn()` helper, Tailwind v3/v4 configs.
1
+ # Changelog
2
+
3
+ All notable changes to the `astralkit` SDK package.
4
+
5
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [0.3.3] — 2026-04-22
9
+
10
+ ### Changed
11
+ - Widened `tailwind-merge` dependency range from `^2.2.0` to `^2.2.0 || ^3.0.0`. Tailwind CSS v4 projects use `tailwind-merge@v3` (which adds v4 class-name recognition), so accepting either major version lets npm dedupe to the host project's copy instead of nesting a second `node_modules/astralkit/node_modules/tailwind-merge`. Same `twMerge` API in both; no SDK code change required.
12
+
13
+ ## [0.3.2] — 2026-04-19
14
+
15
+ ### Fixed (revert of accidental change in 0.3.0 / 0.3.1)
16
+ - **`astralkit/theme` export restored to the Tailwind v3 file (`astralkit-theme.css`, `:root` syntax).** This matches the 0.2.x default and is the designed behavior: v3 is the primary customer base, so the default export targets v3. Projects that pinned `0.3.0` or `0.3.1` saw this default silently flip to v4, which broke any v3 project with `@import "astralkit/theme"` in its CSS.
17
+ - `astralkit/theme-v4` export unchanged still the explicit opt-in for Tailwind v4 projects.
18
+ - Removed the short-lived `astralkit/theme-v3` alias introduced in 0.3.0/0.3.1. If you added it to your CSS during that window, change it back to `astralkit/theme`.
19
+
20
+ ### Migrating from 0.3.0 / 0.3.1
21
+ - **Tailwind v3 projects**: no action — your existing `@import "astralkit/theme"` now resolves to the v3 file again, as it did in 0.2.x.
22
+ - **Tailwind v4 projects**: ensure your CSS uses `@import "astralkit/theme-v4"` (not `"astralkit/theme"`). The AstralKit main app and `astralkit init` for v4 projects already use the explicit `theme-v4` form.
23
+
24
+ ## [0.3.1] — 2026-04-18 (superseded — do not use for new installs)
25
+
26
+ ### Added
27
+ - `peerDependencies` declaration: `tailwindcss >= 3.0.0`. Installing `astralkit` in a project without Tailwind now surfaces a clear peer-dep warning instead of silent breakage.
28
+ - File header comment on `astralkit-theme.css` marking it as the Tailwind v3 file.
29
+
30
+ ### Known issue (fixed in 0.3.2)
31
+ - The `astralkit/theme` export was flipped to resolve to the v4 file — unintentional. Any v3 project that upgraded from `0.2.x` silently started pulling v4 CSS. Use `0.3.2`.
32
+
33
+ ## [0.3.0] — 2026-04-18 (superseded — do not use for new installs)
34
+
35
+ ### Added
36
+ - v4 theme refinements across 12 commits of token architecture work (rail/panel elevated colors, sidebar tokens, avatar sizes, Phase A standardization).
37
+ - `primitives/.npmignore` excludes `*.backup` and `*.pre-v4-split` scratch files from published tarballs (~220 kB removed).
38
+
39
+ ### Fixed
40
+ - Tailwind v3 plugin registration (via CLI init) now covers additional `plugins: [...]` formatting variants.
41
+
42
+ ### Known issue (fixed in 0.3.2)
43
+ - Same `astralkit/theme` export mis-resolution as 0.3.1. Use `0.3.2`.
44
+
45
+ ## [0.2.0] — 2026-04-02
46
+
47
+ ### Added
48
+ - Initial public release on npm.
49
+ - Design tokens (theme CSS), utilities CSS, palette presets, primitives folder, `cn()` helper, Tailwind v3/v4 configs.
package/LICENSE CHANGED
@@ -1,34 +1,34 @@
1
- AstralKit License
2
-
3
- Copyright (c) 2025-2026 Blue Beacon Creative LLC. All rights reserved.
4
-
5
- This software and associated files (the "Software") are the proprietary
6
- intellectual property of Blue Beacon Creative LLC. The Software is licensed,
7
- not sold.
8
-
9
- The design tokens and CSS utilities included in this package are freely usable
10
- in any project that uses AstralKit components. Components, boosters, and
11
- workflows installed via the AstralKit CLI are governed by the AstralKit End
12
- User License Agreement.
13
-
14
- PROHIBITED USES
15
-
16
- You may NOT, without the express prior written consent of Blue Beacon Creative LLC:
17
-
18
- 1. Use the Software's source code as training data, fine-tuning data, or input
19
- for any artificial intelligence system, machine learning model, large language
20
- model, neural network, or any automated system designed to generate code,
21
- text, images, or other output.
22
-
23
- 2. Resell, sublicense, or redistribute the Software as a standalone product,
24
- design system, or token library.
25
-
26
- 3. Build a competing product using the Software's design tokens, CSS
27
- architecture, or utility system.
28
-
29
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
30
- IMPLIED. IN NO EVENT SHALL BLUE BEACON CREATIVE LLC BE LIABLE FOR ANY CLAIM,
31
- DAMAGES OR OTHER LIABILITY.
32
-
33
- Full license terms: https://astralkit.com/license
34
- Contact: hello@astralkit.com
1
+ AstralKit License
2
+
3
+ Copyright (c) 2025-2026 Blue Beacon Creative LLC. All rights reserved.
4
+
5
+ This software and associated files (the "Software") are the proprietary
6
+ intellectual property of Blue Beacon Creative LLC. The Software is licensed,
7
+ not sold.
8
+
9
+ The design tokens and CSS utilities included in this package are freely usable
10
+ in any project that uses AstralKit components. Components, boosters, and
11
+ workflows installed via the AstralKit CLI are governed by the AstralKit End
12
+ User License Agreement.
13
+
14
+ PROHIBITED USES
15
+
16
+ You may NOT, without the express prior written consent of Blue Beacon Creative LLC:
17
+
18
+ 1. Use the Software's source code as training data, fine-tuning data, or input
19
+ for any artificial intelligence system, machine learning model, large language
20
+ model, neural network, or any automated system designed to generate code,
21
+ text, images, or other output.
22
+
23
+ 2. Resell, sublicense, or redistribute the Software as a standalone product,
24
+ design system, or token library.
25
+
26
+ 3. Build a competing product using the Software's design tokens, CSS
27
+ architecture, or utility system.
28
+
29
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
30
+ IMPLIED. IN NO EVENT SHALL BLUE BEACON CREATIVE LLC BE LIABLE FOR ANY CLAIM,
31
+ DAMAGES OR OTHER LIABILITY.
32
+
33
+ Full license terms: https://astralkit.com/license
34
+ Contact: hello@astralkit.com
package/README.md CHANGED
@@ -1,58 +1,71 @@
1
- # astralkit
2
-
3
- Design tokens, CSS variables, and utilities for [AstralKit](https://astralkit.com) UI components.
4
-
5
- This package provides the foundation that all AstralKit components depend on:
6
-
7
- - **Theme CSS** — `ak-*` design tokens (colors, spacing, typography, radius, shadows)
8
- - **Utilities CSS** — Tailwind CSS utility class extensions
9
- - **`cn()` helper** — Class merging utility (clsx + tailwind-merge)
10
-
11
- ## Installation
12
-
13
- ```bash
14
- npm install astralkit
15
- ```
16
-
17
- Or use the CLI which installs this automatically:
18
-
19
- ```bash
20
- npx @astralkit/cli init
21
- ```
22
-
23
- ## Usage
24
-
25
- **In your CSS:**
26
- ```css
27
- @import "tailwindcss";
28
- @import "astralkit/theme";
29
- @import "astralkit/utilities";
30
- ```
31
-
32
- **In your components:**
33
- ```tsx
34
- import { cn } from 'astralkit/utils'
35
-
36
- export function Button({ className, ...props }) {
37
- return <button className={cn('px-4 py-2 bg-ak-primary text-ak-on-primary', className)} {...props} />
38
- }
39
- ```
40
-
41
- ## What's included
42
-
43
- | Export | Description |
44
- |---|---|
45
- | `astralkit/theme` | CSS custom properties for all design tokens |
46
- | `astralkit/utilities` | Tailwind CSS utility extensions |
47
- | `astralkit/utils` | `cn()` class merging function |
48
-
49
- ## Documentation
50
-
51
- - [Getting Started](https://astralkit.com/documentation/quick-start)
52
- - [Design Tokens](https://astralkit.com/documentation/design-tokens)
53
- - [CSS Variables Reference](https://astralkit.com/documentation/css-variables-reference)
54
- - [Theming & Customization](https://astralkit.com/documentation/theming-customization)
55
-
56
- ## License
57
-
58
- Proprietary [AstralKit License](https://astralkit.com/license)
1
+ # astralkit
2
+
3
+ Design tokens, CSS variables, and utilities for [AstralKit](https://astralkit.com) UI components.
4
+
5
+ This package provides the foundation that all AstralKit components depend on:
6
+
7
+ - **Theme CSS** — `ak-*` design tokens (colors, spacing, typography, radius, shadows)
8
+ - **Utilities CSS** — Tailwind CSS utility class extensions
9
+ - **`cn()` helper** — Class merging utility (clsx + tailwind-merge)
10
+
11
+ ## Installation
12
+
13
+ ```bash
14
+ npm install astralkit
15
+ ```
16
+
17
+ Or use the CLI which installs this automatically:
18
+
19
+ ```bash
20
+ npx @astralkit/cli init
21
+ ```
22
+
23
+ ## Usage
24
+
25
+ **In your CSS — Tailwind v3 (default):**
26
+ ```css
27
+ @tailwind base;
28
+ @tailwind components;
29
+ @tailwind utilities;
30
+ @import "astralkit/theme";
31
+ @import "astralkit/utilities";
32
+ ```
33
+
34
+ > Also add `require('astralkit/tailwind.cjs')` to the `plugins` array in your `tailwind.config.js`. `astralkit init` does this for you.
35
+
36
+ **In your CSS Tailwind v4:**
37
+ ```css
38
+ @import "tailwindcss";
39
+ @import "astralkit/theme-v4";
40
+ @import "astralkit/utilities";
41
+ ```
42
+
43
+ **In your components:**
44
+ ```tsx
45
+ import { cn } from 'astralkit/utils'
46
+
47
+ export function Button({ className, ...props }) {
48
+ return <button className={cn('px-4 py-2 bg-ak-primary text-ak-on-primary', className)} {...props} />
49
+ }
50
+ ```
51
+
52
+ ## What's included
53
+
54
+ | Export | Description |
55
+ |---|---|
56
+ | `astralkit/theme` | Design tokens as CSS custom properties (Tailwind **v3** — default) |
57
+ | `astralkit/theme-v4` | Design tokens via the Tailwind v4 `@theme` directive |
58
+ | `astralkit/utilities` | Tailwind CSS utility extensions (works with v3 and v4) |
59
+ | `astralkit/tailwind.cjs` | Tailwind v3 plugin — registers `ak-*` tokens with the v3 config |
60
+ | `astralkit/utils` | `cn()` class merging function |
61
+
62
+ ## Documentation
63
+
64
+ - [Getting Started](https://astralkit.com/documentation/quick-start)
65
+ - [Design Tokens](https://astralkit.com/documentation/design-tokens)
66
+ - [CSS Variables Reference](https://astralkit.com/documentation/css-variables-reference)
67
+ - [Theming & Customization](https://astralkit.com/documentation/theming-customization)
68
+
69
+ ## License
70
+
71
+ Proprietary — [AstralKit License](https://astralkit.com/license)