@usenaive-sdk/blueprints 0.7.0 → 0.9.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.
Files changed (4) hide show
  1. package/dist/index.d.ts +238 -66
  2. package/dist/index.js +1275 -678
  3. package/dist/index.js.map +1 -1
  4. package/package.json +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@usenaive-sdk/blueprints",
3
- "version": "0.7.0",
3
+ "version": "0.9.0",
4
4
  "description": "Declare a project once and reconcile it — the engine behind `naive up`.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -30,7 +30,7 @@
30
30
  "dependencies": {
31
31
  "jiti": "^2.7.0",
32
32
  "zod": "^4.4.3",
33
- "@usenaive-sdk/vetta": "^0.5.0"
33
+ "@usenaive-sdk/vetta": "^0.6.0"
34
34
  },
35
35
  "//devDependencies": "`@vetta/core` is a BUILD-time dependency only, exactly as in `packages/sdk`. It is `private: true` at `0.0.0`, `workspace:*` is rewritten to `0.0.0` on publish, and `npm install` would 404 for every consumer. `build.mjs` inlines it into `dist/` and then fails the build if either `dist/index.js` or `dist/index.d.ts` still names it. Keep it out of `dependencies`. `@usenaive-sdk/vetta` is the opposite case: published, so the workspace protocol is rewritten to a version that resolves, and it stays external so a consumer holds one client, not two. It is `workspace:^`, not `workspace:*`: `*` rewrites to an EXACT pin, which is how a packed engine came out depending on `@usenaive-sdk/vetta` `0.2.0` — a registry version with no `apps` namespace, so the published engine would have installed cleanly and thrown on the first `up`. `^` rewrites to `^<version>`, which admits the patches of the minor that has `apps` and refuses the ones that do not. `build.mjs` enforces the floor.",
36
36
  "devDependencies": {