@atelier-ui/create-workspace 0.2.44 → 0.3.0
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,3 +1,30 @@
|
|
|
1
|
+
## 0.3.0 (2026-09-13)
|
|
2
|
+
|
|
3
|
+
### 🩹 Fixes
|
|
4
|
+
|
|
5
|
+
- ⚠️ **react:** the published package declares what it actually ships ([68a3b528](https://github.com/DominikPieper/atelier-ui/commit/68a3b528))
|
|
6
|
+
|
|
7
|
+
### ⚠️ Breaking Changes
|
|
8
|
+
|
|
9
|
+
- **react:** the published package declares what it actually ships ([68a3b528](https://github.com/DominikPieper/atelier-ui/commit/68a3b528))
|
|
10
|
+
` footer, and that is a judgement to review
|
|
11
|
+
rather than a claim that nothing changed. An external consumer who imports this
|
|
12
|
+
package in their own Vitest suite was silently protected by the guard and now
|
|
13
|
+
needs the same `inline` entry themselves — semver-honest grounds for a major.
|
|
14
|
+
The footer is left off because on this setup it would likely cut 1.0.0
|
|
15
|
+
automatically on push, and that is the owner's call to make deliberately, not a
|
|
16
|
+
side effect of a bug fix.
|
|
17
|
+
Gates: nx test react 0 (450), nx build react 0, nx lint react 0,
|
|
18
|
+
nx storybook-test react 0 (228, run alone), nx test create-workspace 0 (200),
|
|
19
|
+
nx build create-workspace 0, check-adr-refs 0, prettier --check 0. The CLI e2e
|
|
20
|
+
for react — scaffold, build, Storybook build, check:contracts, nx test,
|
|
21
|
+
check:stories in Chromium — green against the fixed package.
|
|
22
|
+
|
|
23
|
+
### ❤️ Thank You
|
|
24
|
+
|
|
25
|
+
- Claude Opus 5 (1M context)
|
|
26
|
+
- Dominik Pieper @DominikPieper
|
|
27
|
+
|
|
1
28
|
## 0.2.44 (2026-09-13)
|
|
2
29
|
|
|
3
30
|
### 🚀 Features
|
package/package.json
CHANGED
|
@@ -17,5 +17,26 @@ export default defineConfig({
|
|
|
17
17
|
environment: 'jsdom',
|
|
18
18
|
include: ['src/**/*.spec.*'],
|
|
19
19
|
setupFiles: ['src/test-setup.ts'],
|
|
20
|
+
server: {
|
|
21
|
+
deps: {
|
|
22
|
+
// @atelier-ui/react's built entry ships one `import './x.css'` per
|
|
23
|
+
// component, same as @atelier-ui/vue's (see that file's version of
|
|
24
|
+
// this comment for the general shape of the problem). Its
|
|
25
|
+
// package.json declares "type": "module" honestly (ADR-0138) and an
|
|
26
|
+
// unqualified `main`/`module`, so Vitest's dual-package guard sees a
|
|
27
|
+
// normal, self-consistent ESM package and hands it to Node's own
|
|
28
|
+
// module loader instead of Vite's — which then fails twice over:
|
|
29
|
+
// Node's loader has no idea what to do with a bare `.css` specifier
|
|
30
|
+
// ("Unknown file extension \".css\""), and even before it gets that
|
|
31
|
+
// far, the package's own extensionless relative imports (emitted by
|
|
32
|
+
// its `"module": "preserve"` / `"moduleResolution": "bundler"` build,
|
|
33
|
+
// which assumes a bundler resolves them) fail Node's stricter ESM
|
|
34
|
+
// resolver on their own ("Cannot find module … imported from …").
|
|
35
|
+
// `inline` forces this one package back through Vite's own
|
|
36
|
+
// pipeline, which resolves both the extensionless imports and the
|
|
37
|
+
// `.css` import the same way it does for every other package here.
|
|
38
|
+
inline: ['@atelier-ui/react'],
|
|
39
|
+
},
|
|
40
|
+
},
|
|
20
41
|
},
|
|
21
42
|
});
|
|
@@ -35,14 +35,14 @@ export default defineConfig({
|
|
|
35
35
|
// resolves component-level CSS imports for every OTHER package here.
|
|
36
36
|
// `inline` forces this one package back through Vite's own pipeline,
|
|
37
37
|
// where the `.css` import is handled like any other test asset.
|
|
38
|
-
// (
|
|
39
|
-
//
|
|
40
|
-
//
|
|
41
|
-
//
|
|
42
|
-
//
|
|
43
|
-
//
|
|
44
|
-
//
|
|
45
|
-
//
|
|
38
|
+
// (@atelier-ui/react's built entry has the identical per-component
|
|
39
|
+
// `import './x.css'` pattern and, since ADR-0138 corrected its
|
|
40
|
+
// package.json to declare "type": "module" honestly, needs this
|
|
41
|
+
// exact same `inline` entry too — see the React version of this
|
|
42
|
+
// file. Before that fix, React's self-contradictory package.json
|
|
43
|
+
// tripped Vitest's dual-package guard and got force-inlined as a
|
|
44
|
+
// side effect of the defect, which is exactly why it was a defect
|
|
45
|
+
// and not a fix.)
|
|
46
46
|
inline: ['@atelier-ui/vue'],
|
|
47
47
|
},
|
|
48
48
|
},
|