update astro 5.1.8 (#155)

Author: JLarky

README.md

@@ -117,7 +117,7 @@ Drizzle migrations happen in two steps: the first step generates a migration fil
 To generate a migration file, run
 
 ```sh
-doppler run yarn drizzle-kit generate:pg
+doppler run yarn drizzle-kit generate
 ```
 
 This will generate a file called something like `src/db/migration/1234_xyz.sql`. Under normal circumstances, you wouldn't have to worry about this file - it will contain an auto-generated set of SQL statements needed to apply the changes expressed in your `schema.ts` to the database. However, since we're using Supabase Postgres, we have to take care of [Row Level Security](https://supabase.com/docs/guides/auth/row-level-security) policies when creating new tables.
@@ -295,7 +295,7 @@ const count = await helpers.counter.getCount.fetch();
 
 Note that in Astro, the code between `---` (called "frontmatter") runs on the server and is not sent to the client.
 
-You can think of `export const prerender = ...` as a per-route switch between SSG and SSR. `prerender = true` means "build-time" (SSG), and `prerender = false` means "request-time" (SSR). If `export const prerender` isn't defined, its default value depends on the value of `output` in the `astro.config.mjs` settings file. In our case, `output` is `hybrid`, which means `prerender = true` by default. For more info on this, see https://docs.astro.build/en/guides/server-side-rendering/.
+You can think of `export const prerender = ...` as a per-route switch between SSG and SSR. `prerender = true` means "build-time" (SSG), and `prerender = false` means "request-time" (SSR). If `export const prerender` isn't defined, its default value depends on the value of `output` in the `astro.config.mjs` settings file. In our case, `output` is `static`, which means `prerender = true` by default. For more info on this, see https://docs.astro.build/en/guides/server-side-rendering/.
 
 If you're familiar with other full-stack frameworks, using `prerender = false` is similar to `getServerSideProps` in Next.js and `loader` in Remix, while `prerender = true` is similar to getStaticProps in Next.js.
 

astro.config.mjs

@@ -1,15 +1,12 @@
 import react from '@astrojs/react';
-import vercel from '@astrojs/vercel/serverless';
+import vercel from '@astrojs/vercel';
 import { defineConfig } from 'astro/config';
 import checker from 'vite-plugin-checker';
 
 // https://astro.build/config
 export default defineConfig({
 	integrations: [react()],
-	output: 'hybrid',
-	adapter: vercel({
-		functionPerRoute: false,
-	}),
+	adapter: vercel({}),
 	// eslint-disable-next-line no-undef
 	site: process.env.SITE_URL,
 	vite: {

package.json

@@ -19,9 +19,9 @@
     "astro": "astro"
   },
   "dependencies": {
-    "@astrojs/check": "0.9.2",
-    "@astrojs/react": "3.6.2",
-    "@astrojs/vercel": "7.7.2",
+    "@astrojs/check": "0.9.4",
+    "@astrojs/react": "4.1.6",
+    "@astrojs/vercel": "8.0.3",
     "@propelauth/base-elements": "^0.0.16",
     "@propelauth/node": "^2.1.0",
     "@propelauth/react": "2.1.0-beta.4",
@@ -37,7 +37,7 @@
     "@types/jsonwebtoken": "^9.0.2",
     "@types/react": "^18.0.21",
     "@types/react-dom": "^18.0.6",
-    "astro": "4.13.3",
+    "astro": "5.1.8",
     "astro-seo": "^0.7.2",
     "clsx": "^1.2.1",
     "cookie": "^0.5.0",

src/components/head/CheckerOverlay.astro

@@ -1 +1 @@
-<script type="module" src="/@vite-plugin-checker-runtime-entry"></script>
+<script is:inline type="module" src="/@vite-plugin-checker-runtime-entry"></script>

src/content/eject/vercel.md

@@ -11,19 +11,18 @@ To remove the Vercel adapter, follow these steps:
 
 ```diff
 import react from '@astrojs/react';
-- import vercel from '@astrojs/vercel/serverless';
+- import vercel from '@astrojs/vercel';
 import { defineConfig } from 'astro/config';
 
 // https://astro.build/config
 export default defineConfig({
 	integrations: [react()],
-	output: 'hybrid',
 -	adapter: vercel(),
 	// eslint-disable-next-line no-undef
 	site: process.env.SITE_URL,
 ```
 
-<p class="text-sm pl-4">NOTE that you can use regular Astro without SSR adapters (if you remove the <code class="whitespace-nowrap">output: 'hybrid',</code> line). This can be a good option if you already have your own backend, but the Kit does not currently support such a configuration.</p>
+<p class="text-sm pl-4">NOTE that you can use regular Astro without SSR adapters (once you remove the <code class="whitespace-nowrap">adapter: vercel({}),</code> line). This can be a good option if you already have your own backend, but the Kit has some routes that will only work in SSR so you'll have to remove those yourself.</p>
 
 Instead, you can add another Astro SSR adapter from the ones available on https://docs.astro.build/en/guides/server-side-rendering/#adding-an-adapter.
 

src/pages/eject/index.astro

@@ -30,7 +30,9 @@ const parsedSteps: {
 }[] = [];
 for (const slug of checksOrder) {
 	const step = await getEntry('eject', slug);
-	parsedSteps.push({ step });
+	if (step) {
+		parsedSteps.push({ step });
+	}
 }
 ---
 

src/pages/setup/index.astro

@@ -29,6 +29,7 @@ const parsedSteps: {
 }[] = [];
 for (const slug of checksOrder) {
 	const step = await getEntry('setup', slug);
+	if (!step) continue;
 	const stepDone = step.data.needsEnv.every((x) => {
 		const value = process.env[x] || import.meta.env[x];
 		return value !== undefined && value !== false;