fix(gatsby-cli): Fix recipes cli invocation (#24201)

gatsbyjs · May 18, 2020 · e6e7463 · e6e7463
1 parent d19567d
commit e6e7463
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 9 deletions.
diff --git a/packages/gatsby-cli/src/create-cli.ts b/packages/gatsby-cli/src/create-cli.ts
@@ -342,15 +342,11 @@ function buildLocalCommands(cli: yargs.Argv, isLocalSite: boolean): void {
   cli.command({
     command: `recipes [recipe]`,
     describe: `[EXPERIMENTAL] Run a recipe`,
-    handler: handlerP(({ recipe }: yargs.Arguments) => {
-      if (typeof recipe !== `string`) {
-        throw new Error(
-          `Error: gatsby recipes needs to be called with a specific recipe`
-        )
+    handler: handlerP(
+      async ({ recipe }: yargs.Arguments<{ recipe: string | undefined }>) => {
+        await recipesHandler(recipe)
       }
-
-      recipesHandler(recipe)
-    }),
+    ),
   })
 }
 

diff --git a/packages/gatsby-cli/src/recipes.ts b/packages/gatsby-cli/src/recipes.ts
@@ -4,7 +4,9 @@ import * as path from "path"
 import * as fs from "fs"
 import detectPort from "detect-port"
 
-export async function recipesHandler(recipe: string): Promise<void> {
+export async function recipesHandler(
+  recipe: string | undefined
+): Promise<void> {
   // We don't really care what port is used for GraphQL as it's
   // generally only for code to code communication or debugging.
   const graphqlPort = await detectPort(4000)