@dunx/create-app 3.3.0 → 3.3.1

package/README.md

@@ -112,7 +112,7 @@ fails if the two ever drift.
 
 Every app also gets an `AGENTS.md` naming its layout, its commands and the rules
 dunx fails at boot over, plus a `CLAUDE.md` pointing at it. Both link
-<https://petarzarkov.github.io/dunx/setup.md>, which is served per release, rather
+<https://dunx.win/setup.md>, which is served per release, rather
 than copying the framework's own instructions into your repository.
 
 The example is the one CI boots, so keeping them identical makes the template

package/dist/{chunk-szd4jhfn.js → chunk-nznx4cv8.js}

@@ -344,8 +344,8 @@ import { fileURLToPath } from "url";
 var {Glob } = globalThis.Bun;
 
 // src/agents.ts
-var SETUP_URL = "https://petarzarkov.github.io/dunx/setup.md";
-var LLMS_URL = "https://petarzarkov.github.io/dunx/llms.txt";
+var SETUP_URL = "https://dunx.win/setup.md";
+var LLMS_URL = "https://dunx.win/llms.txt";
 var CLAUDE_POINTER = `# CLAUDE.md
 
 The instructions for this application live in \`AGENTS.md\`, imported below so every

package/dist/cli.js

@@ -9,7 +9,7 @@ import {
   isValidPackageName2,
   packageVersion,
   scaffold2
-} from "./chunk-szd4jhfn.js";
+} from "./chunk-nznx4cv8.js";
 
 // src/cli.ts
 import { parseArgs } from "util";

package/dist/index.js

@@ -8,7 +8,7 @@ import {
   ScaffoldError2,
   isValidPackageName2,
   scaffold2
-} from "./chunk-szd4jhfn.js";
+} from "./chunk-nznx4cv8.js";
 export {
   FEATURES2 as FEATURES,
   ScaffoldError2 as ScaffoldError,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dunx/create-app",
-  "version": "3.3.0",
+  "version": "3.3.1",
   "description": "Scaffold a new dunx application - bunx @dunx/create-app my-api",
   "keywords": [
     "bun",