create-strapi-launchpad 0.1.0 → 0.1.1

package/README.md

@@ -43,9 +43,9 @@ npx create-strapi-launchpad my-app --framework astro
 - Node.js 20.19 or newer
 - Git
 
-Yarn is required — LaunchPad pins `yarn@4.5.0` in its root `package.json`, so
-npm and pnpm will not work. If yarn is missing, the CLI enables it through
-Corepack for you.
+Yarn is required. Every LaunchPad directory ships a `yarn.lock` and its
+scripts call yarn directly, so that is what the CLI drives. If yarn is
+missing, the CLI enables it through Corepack for you.
 
 ## What it does
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-strapi-launchpad",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "CLI to scaffold the official Strapi LaunchPad demo application with the frontend of your choice",
   "type": "module",
   "bin": {

package/src/commands/create.js

@@ -38,8 +38,10 @@ function normalizeRepo(repo) {
   return { url: `file://${abs}`, local: true };
 }
 
-// LaunchPad pins yarn in its root package.json, so Corepack will refuse any
-// other package manager. There is no point offering a choice.
+// Every LaunchPad directory ships a yarn.lock and its scripts shell out to
+// yarn, so that is what the CLI drives. npm technically runs here, but it
+// would resolve against no lockfile and write a package-lock beside the
+// yarn one.
 const PM = 'yarn';
 
 /**
@@ -333,6 +335,33 @@ export async function createLaunchpadApp(directory, options) {
   log.info(`Strapi admin  → http://localhost:${STRAPI_PORT}/admin`);
   log.info(`${framework.label} → http://localhost:${framework.port}`);
   console.log();
+  // Printed before the dev servers take the terminal over, because their
+  // output scrolls past immediately and this is what people need after the
+  // first Ctrl+C. `yarn dev` is Next for every scaffold, so naming the
+  // frontend-specific script matters.
+  console.log(
+    `  To restart later:  cd ${directory} && ${PM} ${framework.devScript}`
+  );
+  console.log();
+
+  // Ctrl+C sends SIGINT to the whole process group, so Node tears this process
+  // down before anything after the await can run. Handling it explicitly is
+  // the only way to get the last word — without this the message never prints,
+  // which is exactly what happened the first time round.
+  let printed = false;
+  const sayGoodbye = () => {
+    if (printed) return;
+    printed = true;
+    printRestartHelp(directory, framework);
+  };
+  process.on('SIGINT', () => {
+    sayGoodbye();
+    process.exit(0);
+  });
+  process.on('SIGTERM', () => {
+    sayGoodbye();
+    process.exit(0);
+  });
 
   try {
     await execa(PM, [framework.devScript], {
@@ -340,6 +369,36 @@ export async function createLaunchpadApp(directory, options) {
       stdio: 'inherit',
     });
   } catch {
-    // Ctrl+C is the normal way out of a dev server.
+    // The dev servers exiting non-zero is normal on shutdown.
   }
+
+  // Covers the servers stopping on their own rather than by Ctrl+C.
+  sayGoodbye();
+}
+
+/**
+ * Printed when the dev servers stop.
+ *
+ * The same command is shown before they start, but by then it is hundreds of
+ * lines up — a real run buries it under about 280 lines of server output. The
+ * moment someone actually needs it is right after Ctrl+C, so this puts it on
+ * the last line of the terminal.
+ *
+ * `yarn dev` is named explicitly as Next. It is the command people reach for,
+ * and in a scaffold built for another frontend it silently starts the wrong
+ * one — worth saying out loud rather than letting them discover it.
+ */
+function printRestartHelp(directory, framework) {
+  const others = FRAMEWORKS.filter((f) => f.name !== framework.name).map((f) =>
+    f.devScript === 'dev' ? `${PM} dev (${f.label})` : `${PM} ${f.devScript}`
+  );
+
+  console.log();
+  log.info('Stopped.');
+  console.log();
+  console.log(
+    `  Restart:          cd ${directory} && ${PM} ${framework.devScript}`
+  );
+  console.log(`  Other frontends:  ${others.join(', ')}`);
+  console.log();
 }

package/src/utils/prerequisites.js

@@ -37,9 +37,9 @@ export async function checkPrerequisites() {
     process.exit(1);
   }
 
-  // LaunchPad pins yarn@4.5.0 in its root package.json, so this is the only
-  // package manager that will work. Corepack ships with Node and can provide
-  // it without a global install.
+  // Every LaunchPad directory ships a yarn.lock and its scripts shell out to
+  // yarn, so that is what the CLI drives. Corepack comes with Node and can
+  // provide yarn without a global install.
   try {
     await execaCommand('yarn --version');
     log.success('Yarn available');
@@ -54,7 +54,8 @@ export async function checkPrerequisites() {
           '  corepack enable\n' +
           '  — or —\n' +
           '  npm install -g yarn\n\n' +
-          'LaunchPad pins yarn@4.5.0, so npm and pnpm will not work.'
+          'LaunchPad is set up for yarn: every directory ships a yarn.lock\n' +
+          'and its scripts call yarn directly.'
       );
       process.exit(1);
     }