This documentation is for a legacy version of Remix Supabase. For the latest version, please visit the Remix Supabase Turbo documentation

Project Structure

A quick overview of the project structure and how to navigate it.

When inspecting the project structure, you will find something similar to the below:

tasks-app ├── ├── @types ├── src │ ├── components │ ├── core │ ├── lib │ └── routes ... │ └── root.tsx ├── package-lock.json ├── package.json ├── public │ └── favicon.ico └── tsconfig.json

NB: we omitted a lot of the files for simplicity.

Let's take a deeper look at the structure we see above:

  • src/core: this folder contains reusable building blocks of the template that are not related to any domain. This includes components, React hooks, functions, and so on.
  • src/components: this folder contains the application's components, including those that belong to your application's domain. For example, we can add the tasks components to src/components/tasks.
  • src/lib: this folder contains the business logic of your application's domain. For example, we can add the tasks hooks to write and fetch data from Supabase in src/lib/tasks.
  • src/routes: this is Remix folder where we add our application routes.

Don't worry if this isn't clear yet! We'll explain where we place our files in the sections ahead.

Subscribe to our Newsletter
Get the latest updates about React, Remix, Next.js, Firebase, Supabase and Tailwind CSS