fix: move cliInitializedAt call higher in init flow

sanity-io · Oct 1, 2024 · 5a4e770 · 5a4e770
1 parent 306a671
commit 5a4e770
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/packages/@sanity/cli/src/actions/init-project/initProject.ts b/packages/@sanity/cli/src/actions/init-project/initProject.ts
@@ -594,11 +594,8 @@ export default async function initSanity(
 
   trace.log({step: 'importTemplateDataset', selectedOption: shouldImport ? 'yes' : 'no'})
 
-  // Bootstrap Sanity, creating required project files, manifests etc
-  await bootstrapTemplate(templateOptions, context)
-
-  // update that files were initialized locally; do not halt flow for request
-  apiClient({api: {projectId: projectId}})
+  // record that template files attempted to be created locally
+  await apiClient({api: {projectId: projectId}})
     .request<SanityProject>({uri: `/projects/${projectId}`})
     .then((project: SanityProject) => {
       if (!project?.metadata?.cliInitializedAt) {
@@ -615,6 +612,9 @@ export default async function initSanity(
       debug('Failed to update cliInitializedAt metadata')
     })
 
+  // Bootstrap Sanity, creating required project files, manifests etc
+  await bootstrapTemplate(templateOptions, context)
+
   let pkgManager: PackageManager
 
   // If the user has specified a package manager, and it's allowed use that