1
Intro: Up and Running with Remix
1m 50s
2
Create a New Remix Project Using the remix-create CLI
36s
3
Create Your First Remix Route
1m 6s
4
Fetch Data in Remix Using a Basic Loader
2m 24s
5
Remix Server Code Filename Convention
1m 3s
6
Integrate TypeScript Into a Remix Loader Function
2m 12s
7
Model Data in the Prisma Schema for a Remix App
3m 36s
8
Avoid Over-Fetching in Prisma by Using findMany
1m 35s
9
Create a Dynamic Segment in Remix
3m
10
Process Markdown on the Server Using a Remix Loader
2m
11
Get TypeScript Coverage for Dynamic Parameters in Remix with Invariant
2m 24s
12
Render Nested Routes in Remix
4m 9s
13
Use Remix Actions to Handle Form Submission POST Requests
5m 13s
14
Validate Form Fields in a Remix Action
3m 25s
15
Typing Form Submission Values with tiny-invariant
2m 15s
16
Handle Loading State with Remix useTransition
3m 20s
17
Pre-emptively Load Links with Remix prefetch
2m 24s
18
Expose Specific Environmental Variables to The Client Using Remix
4m 56s
19
Create an Admin User Hook using Remix to Verify Admin Users
2m 43s
20
Hide Admin Routes from Non-Admin Users in a Remix App
4m
21
Allow Admins to Edit Existing Posts on Remix Applications
2m 14s
22
Populate Remix Edit Form with Existing Post Data
1m 38s
23
Add Update Functionality to an Edit Post Page in Remix
3m 55s
24
Add Delete Functionality to Posts Page in Remix
2m 28s
25
Add TypeScript Typing to Admin Routes in a Remix App
1m 37s
26
Handle 404s in Remix with CatchBoundaries
2m 57s
27
Handle Unexpected Errors With Error Boundaries in Remix
4m 28s
28
Deploy a Remix Application to Fly.io
4m 46s
29
Outro: Up and Running with Remix
57s

Remix Server Code Filename Convention

Remix

Share this video with your friends

While you technically can have server functions in your route files, it’s not always the best choice.

For code that you never ever want in your client, it’s a best practice to move them into separate files, and name with the .server convention. For example: posts.server.ts

Course

Up and Running with Remix

Kent C. Doddsinstructor

~ 2 years ago

Note that you can absolutely interact with the database directly in your loader within your route module. I just find that it's typically better from a code organization standpoint to put all database interactions in a separate module.