create-inkan 0.9.1 → 0.9.2

package/README.md

@@ -22,5 +22,5 @@ It asks what it needs. Options skip the questions:
 | `--yes` | the defaults for everything the options leave open |
 | `--force` | write into a folder that is not empty |
 
-This package is `inkan create app` of `@vxnsin/inkan` at the same version; with inkan
+This package is `inkan create app` of `@inkanjs/inkan` at the same version; with inkan
 installed, `npx inkan create app` does the same.

package/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 // npm create inkan [folder] -- [options]: hands everything to `inkan create app` of the
-// @vxnsin/inkan this package depends on, at its own version, so the templates and the
+// @inkanjs/inkan this package depends on, at its own version, so the templates and the
 // CLI that writes them always match. The work is all there; this only finds it.
 
 import { spawnSync } from "node:child_process";
@@ -8,7 +8,7 @@ import { readFileSync } from "node:fs";
 import { createRequire } from "node:module";
 import { dirname, join } from "node:path";
 
-const CORE = "@vxnsin/inkan";
+const CORE = "@inkanjs/inkan";
 
 const require = createRequire(import.meta.url);
 const manifest = require.resolve(`${CORE}/package.json`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-inkan",
-  "version": "0.9.1",
+  "version": "0.9.2",
   "description": "npm create inkan: a new inkan app with a store, auth, a frontend, tests and CI, from the inkan of the same version.",
   "keywords": [
     "inkan",
@@ -31,6 +31,6 @@
     "node": ">=22"
   },
   "dependencies": {
-    "@vxnsin/inkan": "0.9.1"
+    "@inkanjs/inkan": "0.9.2"
   }
 }