hazo_ui 6.3.0 → 6.3.1

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.
Files changed (2) hide show
  1. package/CHANGE_LOG.md +31 -0
  2. package/package.json +7 -8
package/CHANGE_LOG.md CHANGED
@@ -5,6 +5,37 @@ All notable changes to this project will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## v6.3.1 (2026-07-29)
9
+
10
+ ### Fixed — test-app builds again
11
+
12
+ `npm run build:test-app` had been failing, which meant the 15 harness cases
13
+ added in 6.3.0 were never actually executed. Three separate causes, all in the
14
+ test-app rather than the library:
15
+
16
+ - The package had no `build:test-app` script at all (it used non-standard
17
+ `test:build` / `test:dev` names), and the test-app called `next` directly
18
+ instead of going through the `scripts/next.mjs` launcher the workspace
19
+ standard requires. Both adopted; `dev:test-app`/`build:test-app` are now the
20
+ entry points and `PORT` defaults to 3300.
21
+ - `next build` died with "ESM packages (hazo_core) need to be imported" via
22
+ `hazo_connect`'s ESM dist. Fixed with `experimental.esmExternals: 'loose'`.
23
+ Neither `transpilePackages` nor `serverComponentsExternalPackages` helps
24
+ here — the latter matches bare package specifiers, and the workspace symlink
25
+ makes the import trace resolve to a relative path that never matches.
26
+ - Type-check then failed on `CSSProperties is not assignable to
27
+ CSSProperties`: two `@types/react` copies (root 18.3.31, nested 18.3.28),
28
+ with source-aliased `hazo_ui` resolving against one and the test-app's own
29
+ files against the other. Pinned both to the root copy via tsconfig `paths`.
30
+
31
+ ### Note on release history
32
+
33
+ `v6.2.0` was committed but never published; `v6.3.0` was published to npm on
34
+ 2026-07-21 *before* its source was committed. npm therefore went
35
+ 6.1.0 → 6.3.0, and for eight days git and npm disagreed about what 6.3.0 was.
36
+ Both are reconciled as of this entry — noted here because neither history
37
+ tells that story on its own.
38
+
8
39
  ## v6.3.0 (2026-07-21)
9
40
 
10
41
  ### New
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "hazo_ui",
3
- "version": "6.3.0",
3
+ "version": "6.3.1",
4
4
  "description": "Set of UI components for common interaction elements in a SaaS app",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -33,18 +33,17 @@
33
33
  "scripts": {
34
34
  "build": "tsup",
35
35
  "dev": "tsup --watch",
36
- "dev:test-app": "cd test-app && npm run dev",
37
- "test:build": "npm run build && cd test-app && npm run build",
38
- "test:dev": "npm run build && npm run dev:test-app",
36
+ "dev:test-app": "npm run build && cd test-app && npm run dev",
39
37
  "lint": "eslint src --ext ts,tsx",
40
38
  "type-check": "tsc --noEmit",
41
- "prepublishOnly": "npm run build && npm run type-check"
39
+ "prepublishOnly": "npm run build && npm run type-check",
40
+ "build:test-app": "npm run build && cd test-app && npm run build"
42
41
  },
43
42
  "peerDependencies": {
44
43
  "react": "^18.0.0 || ^19.0.0",
45
44
  "react-dom": "^18.0.0 || ^19.0.0",
46
- "hazo_core": "^1.2.1",
47
- "hazo_state": "^0.1.2",
45
+ "hazo_core": "^1.3.0",
46
+ "hazo_state": "^0.2.0",
48
47
  "hazo_theme": "^1.0.1"
49
48
  },
50
49
  "dependencies": {
@@ -114,7 +113,7 @@
114
113
  "@types/canvas-confetti": "^1.9.0",
115
114
  "@types/react": "^18.3.3",
116
115
  "@types/react-dom": "^18.3.0",
117
- "hazo_core": "^1.2.1",
116
+ "hazo_core": "^1.3.0",
118
117
  "hazo_theme": "^1.0.1",
119
118
  "postcss": "^8.4.49",
120
119
  "react": "^18.3.1",