create-deka-app 0.0.4 → 0.0.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-deka-app",
-  "version": "0.0.4",
+  "version": "0.0.6",
   "description": "Scaffold a new deka app",
   "bin": {
     "create-deka-app": "./index.js"

package/src/scaffold.js

@@ -29,6 +29,41 @@ function dekaBinPath(targetDir, platform) {
   return path.join(targetDir, 'node_modules', '.bin', platform === 'win32' ? 'deka.cmd' : 'deka')
 }
 
+// `deka init`'s own "next steps" block always starts with a line beginning
+// "[init]" (verified against the real binary: `[init] DekaScript app
+// ready` followed by 1-2 indented command lines). Everything from that
+// line onward is deka's suggestion for what to run next, and we always
+// replace it with our own -- see printNextSteps below for why. Everything
+// before it (the banner, the per-file `[create] ...` lines) is left
+// intact so the user still sees the scaffold happen.
+function stripDekaNextSteps(output) {
+  if (!output) return ''
+  const lines = String(output).split(/\r?\n/)
+  const cutIndex = lines.findIndex((line) => line.startsWith('[init]'))
+  return cutIndex === -1 ? String(output) : lines.slice(0, cutIndex).join('\n')
+}
+
+// deka init's own next-steps text always tells the user to run `deka dev`,
+// and that command is correct as-is -- `deka` from this package is scoped
+// to the project, so the copy installed into node_modules/.bin (and picked
+// up via the project's package.json script) works with nothing beyond what
+// the install step above already put on disk. We suppress deka's block
+// (stripDekaNextSteps) only because it doesn't know it's being invoked
+// from the parent directory here, so it can't tell the user they still
+// need to `cd <dirName>` first -- not because its command is wrong. Our
+// own block adds that missing `cd` and repeats `deka dev` verbatim,
+// regardless of which package manager ran the install. (This reverts an
+// earlier version of this function that substituted a package-manager
+// idiom -- `npm run dev` / `pnpm dev` / etc. -- for `deka dev`, on the
+// mistaken premise that a bare `deka dev` can't be run without a global
+// install.)
+function printNextSteps(log, dirName) {
+  log('')
+  log('  Next steps:')
+  log(`    cd ${dirName}`)
+  log('    deka dev')
+}
+
 export const RUNTIME_PACKAGE = '@dekaruntime/deka'
 
 // Builds the package.json this package writes into every scaffolded
@@ -168,17 +203,38 @@ export function createApp({
     )
   }
 
-  const init = spawn(dekaBin, ['init'], { cwd: targetDir, stdio: 'inherit' })
+  // Invoked as `deka init <dirName>` from the *parent* directory -- the
+  // same shape as someone typing `deka init myapp` by hand -- rather than
+  // `deka init` with cwd already set to targetDir. deka init never
+  // overwrites a file that already exists (package.json, written above,
+  // survives untouched), and this shape is what makes deka's own output
+  // reference the right directory name if any of it leaks through.
+  const dirName = path.basename(targetDir)
+  const parentDir = path.dirname(targetDir)
+  const init = spawn(dekaBin, ['init', dirName], {
+    cwd: parentDir,
+    stdio: ['inherit', 'pipe', 'pipe'],
+    encoding: 'utf8',
+  })
 
   if (init.error) {
     throw new ScaffoldError(`Could not run "deka init" in ${targetDir}: ${init.error.message}`)
   }
   if (init.status !== 0) {
+    // Something went wrong -- show everything deka printed, unfiltered,
+    // so the real error is visible. Filtering only ever happens below, on
+    // the success path, where we know exactly what we're throwing away.
+    if (init.stdout) log(String(init.stdout))
+    if (init.stderr) log(String(init.stderr))
     throw new ScaffoldError(
       `"deka init" failed in ${targetDir} (exit code ${init.status}).`,
       init.status ?? 1
     )
   }
 
+  if (init.stdout) log(stripDekaNextSteps(init.stdout))
+  if (init.stderr) log(stripDekaNextSteps(init.stderr))
+  printNextSteps(log, dirName)
+
   return 0
 }