Once you've created a project and installed dependencies with
pnpm iAlso make sure you have the supabase CLI installed. If you don't, you can do so by running
brew install supabase/tap/supabaseLink the project with the right supabase project using
supabase link --project-ref [project-ref found in supabase URL]Link to the vercel project using
vercel linkThen pull down the env variables using
vercel env pull .envMake sure docker is running and run
supabase startto start the local supabase database. Existing migrations and supabase/seed.sql will be run on that database.
Then run
pnpm run devto start the local dev server.
To create a production version of your app:
pnpm run buildYou can preview the production build with pnpm run preview.
If you need to change the schema of the database you can run
supabase migration new [migration_name]to generate a new migration file. Alternatively, you can use the Supabase Studio GUI to make changes to the local database and then generate a schema file based on the diff using
supabase db diff --use-migra -f [migration_name]To keep types between the database and the frontend aligned, run
supabase gen types typescript --local --schema public > src/lib/types/supabase.tswhich will generate a typescript interface which gets injected when creating the supabase client, making the the queries with it completely typesafe.
Some E2E tests are implemented on checkly that run on every new deploy to vercel.
Svelte inspector has been added to the config, so just hit command + shift to enable it and jump directly to the code of the respective components.
Tailwind is used for styling and shadcn-svelte for the component library. Installed components can be found here.
Linear was used to keep track of issues. To link a PR to a Linear issue just put [DX-] into the PR title.