@navecss/core 0.5.0 → 0.6.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/README.md +38 -9
- package/dist/bin.js +3 -3
- package/dist/{chunk-63H2FLGU.js → chunk-B5CWZIBK.js} +1 -1
- package/dist/{chunk-BCUK4M4P.js → chunk-EYMFWE3A.js} +1866 -56
- package/dist/{chunk-MWHZ26S4.js → chunk-KDLLTOAM.js} +6 -34
- package/dist/{chunk-KKUYU75D.js → chunk-R6R5DSTT.js} +1 -1
- package/dist/collect.d.ts +309 -13
- package/dist/collect.js +37 -1
- package/dist/lightningcss.js +3 -3
- package/dist/postcss.js +2 -2
- package/dist/vite.js +109 -914
- package/package.json +11 -12
- package/skills/navecss/SKILL.md +1 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@navecss/core",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.6.0",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "Nave design system — layer architecture, reset, atomic utilities, and the Vite, PostCSS and Lightning CSS adapters and a command line for the @nave directive",
|
|
@@ -98,28 +98,28 @@
|
|
|
98
98
|
}
|
|
99
99
|
},
|
|
100
100
|
"dependencies": {
|
|
101
|
-
"@navecss/tokens": "^0.
|
|
101
|
+
"@navecss/tokens": "^0.6.0"
|
|
102
102
|
},
|
|
103
103
|
"devDependencies": {
|
|
104
|
-
"@astrojs/node": "11.1.
|
|
105
|
-
"@astrojs/react": "7.1.
|
|
104
|
+
"@astrojs/node": "11.1.11",
|
|
105
|
+
"@astrojs/react": "7.1.4",
|
|
106
106
|
"@rmenke/css-tokenizer-tests": "1.4.0",
|
|
107
107
|
"@sveltejs/vite-plugin-svelte": "7.3.1",
|
|
108
108
|
"@types/node": "^26.6.6",
|
|
109
109
|
"@vitejs/plugin-vue": "6.0.10",
|
|
110
|
-
"@vitest/browser": "5.0
|
|
111
|
-
"@vitest/browser-playwright": "5.0
|
|
112
|
-
"@vitest/coverage-v8": "5.0
|
|
110
|
+
"@vitest/browser": "5.1.0",
|
|
111
|
+
"@vitest/browser-playwright": "5.1.0",
|
|
112
|
+
"@vitest/coverage-v8": "5.1.0",
|
|
113
113
|
"astro": "7.4.0",
|
|
114
114
|
"lightningcss": "1.33.0",
|
|
115
115
|
"lightningcss-1-24": "npm:lightningcss@1.24.1",
|
|
116
116
|
"mdn-data": "2.37.2",
|
|
117
|
-
"playwright": "1.
|
|
117
|
+
"playwright": "1.65.0",
|
|
118
118
|
"postcss": "^8.5.32",
|
|
119
119
|
"prettier": "3.9.10",
|
|
120
120
|
"react": "^19.3.0",
|
|
121
121
|
"react-dom": "^19.3.0",
|
|
122
|
-
"sass": "1.
|
|
122
|
+
"sass": "1.108.1",
|
|
123
123
|
"source-map": "^0.8.0",
|
|
124
124
|
"stylelint": "17.16.0",
|
|
125
125
|
"stylelint-16-16": "npm:stylelint@16.16.0",
|
|
@@ -129,9 +129,9 @@
|
|
|
129
129
|
"typescript": "6.0.3",
|
|
130
130
|
"vite": "8.3.5",
|
|
131
131
|
"vite-floor": "npm:vite@8.2.1",
|
|
132
|
-
"vitest": "5.0
|
|
132
|
+
"vitest": "5.1.0",
|
|
133
133
|
"vscode-css-languageservice": "6.3.10",
|
|
134
|
-
"vue": "3.5.
|
|
134
|
+
"vue": "3.5.45"
|
|
135
135
|
},
|
|
136
136
|
"engines": {
|
|
137
137
|
"node": ">=22.18"
|
|
@@ -150,7 +150,6 @@
|
|
|
150
150
|
"scripts": {
|
|
151
151
|
"build": "node scripts/build-css.ts && tsup",
|
|
152
152
|
"dev": "tsup --watch",
|
|
153
|
-
"generate:migration-old-placement": "node scripts/generate-migration-old-placement.ts",
|
|
154
153
|
"generate:property-table": "node scripts/generate-property-table.ts",
|
|
155
154
|
"clean": "rm -rf dist",
|
|
156
155
|
"typecheck": "tsc --noEmit && tsc --noEmit -p test/browser/tsconfig.json",
|
package/skills/navecss/SKILL.md
CHANGED
|
@@ -70,7 +70,7 @@ built-in atom it names, and `cx()` takes built-in atoms and nothing else.
|
|
|
70
70
|
Its type check is TypeScript only: a JavaScript consumer gets none of it. A type error from
|
|
71
71
|
`cx()` means the name is wrong: it is never a reason to reach for `cx.raw()` or a cast.
|
|
72
72
|
|
|
73
|
-
In a project whose Vite config uses `navePlugin()` from `@navecss/core/vite`, the build reads every `cx()` call and fails on one whose atoms it cannot list. Pass names it can read (a literal, a condition between literals, a `const` in the same file); to choose by a value, call `cx()` once per case and pick between the results; pass a name known only at run time to `cx.dynamic()`, with its atoms in `keep
|
|
73
|
+
In a project whose Vite config uses `navePlugin()` from `@navecss/core/vite`, or whose Next.js config is wrapped in `withNave()` from `@navecss/prune`, the build reads every `cx()` call and fails on one whose atoms it cannot list. On Next.js that means the calls in the JavaScript and TypeScript modules your entry files import: a module that reaches the page another way, such as one that only Markdown or MDX files import or one loaded through `import()` or `require()` with a specifier built at run time, is not read, and `@navecss/prune`'s README lists what else the build cannot see. Pass names it can read (a literal, a condition between literals, a `const` in the same file); to choose by a value, call `cx()` once per case and pick between the results; pass a name known only at run time to `cx.dynamic()`, with its atoms in `keep`, an option of `navePlugin()` on Vite and of `withNave()` on Next.js. The build's report names its remedies, most preferred first: take the first one that fits; on Next.js, `next dev` prints it in its terminal, not in the browser. Never set `atomic: 'all'`, never move a Next.js project back to `@navecss/core/postcss` or remove `withNave()`, never build a `nave-` class from pieces, and never apply a class taken from `@navecss/core/atoms`, to make a report go away. The dev server serves the atoms the build would ship, chosen from the code it has read, so a `nave-*` class with no rule in dev is written where the build cannot see it: move it into code the build reads, or list its atom in `keep`.
|
|
74
74
|
|
|
75
75
|
## `cx.raw()`
|
|
76
76
|
|