fix: error out if studioBasePath looks like an absolute URL (#211)

* Avoid improperly injecting an Astro route if a non-embedded Studio is used. Besides allowing proper operation with a separate Studio, this also avoids a rather misleading error and its message. * A more clarifying solution to the separated-Studio problem, after conversation with @christianhg * Alter to match changes made by @christianhg two days prior, after the fetch for latest had been taken. * Simplify error message --------- Co-authored-by: Christian Hamburger Grøngaard <[email protected]>
sanity-io · Aug 29, 2024 · 9dc8b72 · 9dc8b72
1 parent 2f7e96c
commit 9dc8b72
Showing 1 changed file with 6 additions and 0 deletions.
diff --git a/packages/sanity-astro/src/index.ts b/packages/sanity-astro/src/index.ts
@@ -18,6 +18,12 @@ export default function sanityIntegration(
   const clientConfig = integrationConfig
   delete clientConfig.studioBasePath
 
+  if (!!studioBasePath && studioBasePath.match(/https?:\/\//)) {
+    throw new Error(
+      "[@sanity/astro]: The `studioBasePath` option should be a relative URL. For example — `studioBasePath: '/admin'`",
+    )
+  }
+
   return {
     name: '@sanity/astro',
     hooks: {