@weft-js/cli 0.1.3 → 0.1.4

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 CHANGED
@@ -15,7 +15,7 @@
15
15
  <a href="https://www.npmjs.com/package/@weft-js/cli"><img src="https://img.shields.io/npm/v/@weft-js/cli?color=145c3c&label=npm" alt="npm version"></a>
16
16
  <a href="https://github.com/Ravonus/weft/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-145c3c" alt="MIT license"></a>
17
17
  <a href="https://github.com/Ravonus/weft/actions"><img src="https://img.shields.io/github/actions/workflow/status/Ravonus/weft/quality.yml?branch=main&label=checks" alt="checks"></a>
18
- <img src="https://img.shields.io/badge/node-%3E%3D26-145c3c" alt="Node 26 or later">
18
+ <img src="https://img.shields.io/badge/node-%3E%3D24-145c3c" alt="Node 24 or later">
19
19
  </p>
20
20
 
21
21
  <p align="center">
@@ -96,7 +96,7 @@ bun add -d @weft-js/cli
96
96
  deno add -D npm:@weft-js/cli
97
97
  ```
98
98
 
99
- It needs Node 26 or later, or Bun or Deno in its place. `@weft-js/core` is a peer dependency: the CLI uses the project's
99
+ It needs Node 24 or later, or Bun or Deno in its place. `@weft-js/core` is a peer dependency: the CLI uses the project's
100
100
  own compiler, and falls back to its own copy only when the project has none.
101
101
 
102
102
  ## Quick start
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@weft-js/cli",
3
- "version": "0.1.3",
3
+ "version": "0.1.4",
4
4
  "description": "The weft command: dev, build, check, the agent layer and the MCP server",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -21,17 +21,17 @@
21
21
  "./config": "./src/config.mjs"
22
22
  },
23
23
  "engines": {
24
- "node": ">=26"
24
+ "node": ">=24"
25
25
  },
26
26
  "dependencies": {
27
- "@weft-js/create": "0.1.3",
27
+ "@weft-js/create": "0.1.4",
28
28
  "axe-core": "4.14.0",
29
29
  "typescript": "6.0.3",
30
30
  "yaml": "2.9.1",
31
31
  "zod": "4.6.7"
32
32
  },
33
33
  "peerDependencies": {
34
- "@weft-js/core": "^0.1.3"
34
+ "@weft-js/core": "^0.1.4"
35
35
  },
36
36
  "publishConfig": {
37
37
  "access": "public"
@@ -60,6 +60,7 @@ function baseSchemas(z) {
60
60
  inlineCss: z.boolean().optional(),
61
61
  criticalCss: z.boolean().optional(),
62
62
  criticalKeep: z.array(z.string()).optional(),
63
+ csp: z.literal('strict').optional(),
63
64
  image: z.union([z.literal('auto'), z.literal(false), z.string().min(1), image]).optional(),
64
65
  card: card.optional(),
65
66
  head: z.string().optional(),
package/src/mcp.mjs CHANGED
@@ -191,7 +191,7 @@ export async function handle(root, msg) {
191
191
  return reply({
192
192
  protocolVersion: versions.includes(asked) ? asked : versions[0],
193
193
  capabilities: { tools: { listChanged: false } },
194
- serverInfo: { name: 'weft', version: '0.1.3' },
194
+ serverInfo: { name: 'weft', version: '0.1.4' },
195
195
  instructions:
196
196
  'weft is a fine-grained reactive TSX framework, not React. Read `docs` topic `rules` first, and run `check` after every edit. Every page sets `meta` from its own context as part of building it (`docs` topic `meta`). Chrome shared across route sections (a sidebar) goes in one layout above them that follows `currentPath()`, never a layout per section (`docs` topic `start`). Style with groups from @weft-js/core/style, not class lists: `style_find` before you write one. Verify behavior in the running app with the browser_* tools (or `__weft__.agent` in your own browser), and run `test_gate` before you call a change done.',
197
197
  })