@dyrected/core 1.0.0 → 1.0.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/dist/index.cjs CHANGED
@@ -55,7 +55,7 @@ IMPORTANT NOTES \u2014 READ BEFORE ACTING
55
55
  - AUTO-SEEDING: Use \`initialData\` in all data fetches to ensure the site is never empty on first load.
56
56
  - Globals use \`client.global(slug).get()\` and \`client.global(slug).update(data)\`.
57
57
  - Relationship fields are populated to the specified \`depth\` (default: 1). Set \`depth: 0\` for IDs only.
58
- - SYNC SCHEMA: After creating the content model, you MUST execute \`npx dyrected sync:schema\` immediately. This is non-negotiable for a working setup.
58
+ - SYNC SCHEMA: After creating the content model, you MUST execute \`npx @dyrected/cli sync:schema\` immediately. This is non-negotiable for a working setup.
59
59
  - EMBED ADMIN: You MUST create a route (e.g. \`/admin\`) and mount the Admin UI components described below.
60
60
  - ALL-IN-ONE: Your goal is to give the user a project that is READY TO SHIP. Do the setup, do the embedding, and do the sync in one go.
61
61
  `;
package/dist/index.js CHANGED
@@ -29,7 +29,7 @@ IMPORTANT NOTES \u2014 READ BEFORE ACTING
29
29
  - AUTO-SEEDING: Use \`initialData\` in all data fetches to ensure the site is never empty on first load.
30
30
  - Globals use \`client.global(slug).get()\` and \`client.global(slug).update(data)\`.
31
31
  - Relationship fields are populated to the specified \`depth\` (default: 1). Set \`depth: 0\` for IDs only.
32
- - SYNC SCHEMA: After creating the content model, you MUST execute \`npx dyrected sync:schema\` immediately. This is non-negotiable for a working setup.
32
+ - SYNC SCHEMA: After creating the content model, you MUST execute \`npx @dyrected/cli sync:schema\` immediately. This is non-negotiable for a working setup.
33
33
  - EMBED ADMIN: You MUST create a route (e.g. \`/admin\`) and mount the Admin UI components described below.
34
34
  - ALL-IN-ONE: Your goal is to give the user a project that is READY TO SHIP. Do the setup, do the embedding, and do the sync in one go.
35
35
  `;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dyrected/core",
3
- "version": "1.0.0",
3
+ "version": "1.0.1",
4
4
  "type": "module",
5
5
  "main": "./dist/index.js",
6
6
  "module": "./dist/index.mjs",
@@ -35,6 +35,17 @@
35
35
  "typescript": "^5.0.0",
36
36
  "vitest": "^1.0.0"
37
37
  },
38
+ "license": "BSL-1.1",
39
+ "author": "Ajola Technologies Ltd",
40
+ "homepage": "https://dyrected.com",
41
+ "repository": {
42
+ "type": "git",
43
+ "url": "git+https://github.com/she-WritesCode/dyrected.git"
44
+ },
45
+ "publishConfig": {
46
+ "access": "public"
47
+ },
48
+ "description": "Core engine and schema handling for Dyrected CMS",
38
49
  "scripts": {
39
50
  "build": "tsup src/index.ts src/server.ts --format cjs,esm --dts",
40
51
  "dev": "tsup src/index.ts src/server.ts --format cjs,esm --watch --dts",