Update readme.md

biome.json

@@ -1,5 +1,5 @@
 {
-  "$schema": "https://biomejs.dev/schemas/1.9.0/schema.json",
+  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
   "organizeImports": {
     "enabled": true
   },

infra/secret.ts

@@ -4,8 +4,7 @@ export const secret = {
   DATABASE_URL: new sst.Secret('DATABASE_URL'),
   STRIPE_PUBLIC_KEY: new sst.Secret('STRIPE_PUBLIC_KEY'),
   STRIPE_SECRET_KEY: new sst.Secret('STRIPE_SECRET_KEY'),
-  // TODO: github auth
-  // GitHubClientId: new sst.Secret('GitHubClientId'),
-  // GitHubClientSecret: new sst.Secret('GitHubClientSecret'),
+  // GITHUB_CLIENT_ID: new sst.Secret('GITHUB_CLIENT_ID'),
+  // GITHUB_CLIENT_SECRET: new sst.Secret('GITGUB_CLIENT_SECRET'),
   HONEYPOT_ENCRYPTION_SEED: new sst.Secret('HONEYPOT_ENCRYPTION_SEED'),
 }

packages/www/vitest.config.ts

@@ -7,10 +7,6 @@ import tsconfigPaths from 'vite-tsconfig-paths'
 export default defineConfig({
   plugins: [tsconfigPaths()],
   test: {
-    // Allows the use of `test` globals in your test files.
-    globals: true,
-    // Disables multi-threading and runs test serially. (Prisma will benefit from this).
-    pool: 'forks',
     // Path to setup file that runs before your tests.
     setupFiles: ['./tests/setup-test-env.ts'],
     // Path to your test files.

README.md → readme.md

@@ -13,6 +13,7 @@ delightful, secure user experiences.
   - [Backend](#backend)
   - [Frontend](#frontend)
 - [When should I use this?](#when-should-i-use-this)
+- [Setup](#setup)
 - [Use](#use)
 - [Acknowledgments](#acknowledgments)
 - [License](#license)
@@ -170,21 +171,22 @@ This template is not designed to be the quickest to set up to play with.
 
 We need to setup a couple of things in order to provision our infrastructure.
 
-1. Domain to host the site and API on. Can be skipped but then you can’t test
+1. **Domain** to host the site and API on. Can be skipped but then you can’t test
    payments.
-2. AWS account to provision the infrastructure.
-3. Neon account with configured database.
-4. Stripe account for payments.
-5. GitHub account for the social login.
-6. Secure secrets for sessions, honeypots, and encryption.
+2. **AWS account** to provision the infrastructure.
+3. **Neon account** with configured database.
+4. **Stripe account** for payments.
+5. **GitHub account** for the social login.
+6. **Secure secrets** for sessions, honeypots, and encryption.
 
 ### Domain
 
 A domain registered with
 [Cloudflare](https://www.cloudflare.com/products/registrar/) or
 [AWS Route 53](https://aws.amazon.com/route53/).
 
-Just kicking the tires? You can skip this but then you can’t test payments as we
+> [!NOTE]
+> Just kicking the tires? You can skip this but then you can’t test payments as we
 need to provision a stable URL for the Stripe webhook.
 
 ### AWS