create-velar 0.29.2 → 0.30.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.
- package/README.md +10 -1
- package/dist/types.d.ts +1 -1
- package/dist/types.js +4 -4
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,5 +1,8 @@
|
|
|
1
1
|
# create-velar
|
|
2
2
|
|
|
3
|
+
**VelarScript 0.30.1.** This package publishes no language surface of its own;
|
|
4
|
+
it writes the exact pins and the `surfaces` block of the release it ships with.
|
|
5
|
+
|
|
3
6
|
The official non-interactive project creator for VelarScript. It is the package
|
|
4
7
|
behind `npm create velar@latest` and shares the same templates with
|
|
5
8
|
`velar create`.
|
|
@@ -25,10 +28,16 @@ application outside that public entry. `game` is reserved for the future
|
|
|
25
28
|
official Canvas framework and deliberately fails until that package exists.
|
|
26
29
|
|
|
27
30
|
Every generated project includes a root `AGENTS.md` that points coding agents
|
|
28
|
-
at its distinct Core/Web/Node/Desktop `velar skill` briefs — packaged with the toolchain — together
|
|
31
|
+
at its distinct Core/Web/Node/Server/Desktop `velar skill` briefs — packaged with the toolchain — together
|
|
29
32
|
with the project's gate commands (`velar check`, `velar test`, `velar format`)
|
|
30
33
|
and the JavaScript escape-hatch ladder.
|
|
31
34
|
|
|
35
|
+
Every generated `velar.json` carries a complete `surfaces` block — `core`, plus
|
|
36
|
+
one entry per activated extension — written from the toolchain that created it,
|
|
37
|
+
so a later upgrade that moves a surface is refused by name rather than let
|
|
38
|
+
through in silence. Dependencies are pinned exactly for the same reason: there
|
|
39
|
+
is no backward-compatibility promise for a range to be safe inside.
|
|
40
|
+
|
|
32
41
|
Creation is transactional. It refuses non-empty targets and never installs
|
|
33
42
|
dependencies, downloads browsers, initializes Git, or contacts a service.
|
|
34
43
|
The generated README keeps the first `npm install` explicit, then points to the
|
package/dist/types.d.ts
CHANGED
package/dist/types.js
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
export const VELAR_CREATE_VERSION = "0.
|
|
1
|
+
export const VELAR_CREATE_VERSION = "0.30.1";
|
|
2
2
|
export const VELAR_PROJECT_FORMAT_VERSION = 2;
|
|
3
3
|
/**
|
|
4
4
|
* D110 rule 5 — the surface versions `velar create` writes into a new project's
|
|
@@ -16,9 +16,9 @@ export const VELAR_PROJECT_FORMAT_VERSION = 2;
|
|
|
16
16
|
* reaches this table in the same commit or not at all.
|
|
17
17
|
*/
|
|
18
18
|
export const VELAR_TEMPLATE_SURFACE_VERSIONS = Object.freeze({
|
|
19
|
-
core: "0.
|
|
20
|
-
web: "0.
|
|
21
|
-
node: "0.
|
|
19
|
+
core: "0.8",
|
|
20
|
+
web: "0.14",
|
|
21
|
+
node: "0.17",
|
|
22
22
|
server: "0.15",
|
|
23
23
|
desktop: "0.10",
|
|
24
24
|
});
|
package/package.json
CHANGED