Remix Todo App: Part 6 - Deploying the App

Step-by-step guidance on how to deploy your Remix Todo App to production.

Remix Todo App: Part 5 - Implementing a Theme Switcher

Add a theme switcher to your Remix Todo App to support light and dark modes.

Remix Todo App: Part 4 - Pending UI

Improve user experience by adding pending states and implementing network-aware UI feedbacks.

Remix Todo App: Part 3 - Multiple Forms with Single Button and Concurrent Mutations

Learn how to implement multiple forms with a single button for mutations and handle concurrent mutations efficiently in Remix.

Remix Todo App: Part 2 - Loading Data into Components and Handling Mutations with Form

Discover how to load data into components and manage mutations using Remix forms.

Remix Todo App: Part 1 - Building the App Layout and Structure

Learn how to set up the layout and structure of your Remix Todo App.

Working with QR codes in Remix | Andre Landgraf

Learn how to easily generate QR codes in your Remix app to share URLs and other information with your users.

EVERYTHING you need to KNOW about Remix.run ACTIONS

Today we go over how actions inside of React Router v7 / Remix.run work. How you submit to them, what happens when you do, how they re-trigger loaders, resource routes, multiple forms on a single page handling. Custom HoC and middleware and much much more! 👍 Don't forget to like, comment, and subscribe for more episodes in this series! Join our coding community and let's build something amazing together. 📌 Stay Connected: Twitter: https://twitter.com/AlemTuzlak GitHub: https://github.com/AlemTuzlak Company Github: https://github.com/forge42dev ⏱️ Timestamps: 00:00 - Intro 00:33 - What are remix actions? 01:04 - Usual submission flow 03:37 - Action submission flow 06:13 - loaders re-triggering flow 07:19 - what you can use re-triggers for 07:59 - Why re-triggers are awesome 08:26 - what happens when you submit to an action? 08:46 - returning response from an action 09:36 - throwing responses 09:57 - throwing a redirect response 10:36 - when is it useful to throw responses 11:02 - throwing non-redirect responses 12:05 - difference between a thrown redirect and normal response 12:53 - useActionData important info 13:45 - resource routes 15:28 - why are resource routes awesome 17:13 - setting up the playground 17:56 - adding a progressively enhanced form 18:37 - triggering an action 19:03 - adding fields to the form 19:37 - seeing our server data 20:23 - progressive enhancement with no JS 22:19 - handling multiple forms on a page with single action 26:05 - handling multiple forms on a page with resource routes & tRPC like loaders 29:59 - redirecting from actions to new routes 31:30 - throwing responses & errors into error boundaries 33:03 - redirecting on successful submissions 33:39 - adding action middleware 35:20 - outro 🔖 Tags: Remix framework, Vite, Remix Vite, web development, frontend development, Remix tutorial, coding tutorial, Remix Vite tutorial, open source, coding community, remix framework tutorial

How Remix's Flat File-Based Routing Works

Learn how Remix's flat file-based routing generates routes from file names.

Everything YOU need to KNOW about Remix loaders

Today we go over how loaders inside of React Router v7 / Remix.run work. How you can cache loaders, how you can optimize them, where and how they re-trigger, and by the end of this video you will be ready to use them for any situation that might come up. 👍 Don't forget to like, comment, and subscribe for more episodes in this series! Join our coding community and let's build something amazing together. 📌 Stay Connected: Twitter: https://twitter.com/AlemTuzlak GitHub: https://github.com/AlemTuzlak Company Github: https://github.com/forge42dev ⏱️ Timestamps: 00:56 - What are loaders exactly? 04:19 - Single fetch approach with loaders 07:40 - What can you return from loaders 08:32 - Successful responses 08:50 - Thrown responses 09:25 - Error responses 09:54 - Streaming the data 11:53 - Streaming the data with single fetch 13:28 - When do loaders re-fire 13:43 - re-fire on action submission 14:40 - re-fire on param change 15:56 - re-fire on search param change 16:37 - re-fire on useRevalidate trigger 17:04 - re-fire on navigation to the same page 18:02 - how to stop loader re-triggers 20:14 - Practical examples 23:29 - Defering slow requests 25:56 - Using server caching for faster response times 28:25 - Caching with headers 30:25 - Using shouldRevalidate 32:44 - clientLoader caching (with remix-client-cache) 32:59 - Defer with single fetch 🔖 Tags: Remix framework, Vite, Remix Vite, web development, frontend development, Remix tutorial, coding tutorial, Remix Vite tutorial, open source, coding community, remix framework tutorial

File uploads with Remix (Updated) — ProgrammingAreHard —

Cache Control and Remix: Answering my own questions

Introduction I had some questions around Cache Control and using them in Remix. This is kind of just me answering my own questions lol. Before going over my questions, let's look at two examples and some of the values. Cache-Control without stale-whi...

Speed up your Remix knowledge

Introduction This post is for my younger self. A post that would've helped me get up to speed with Remix faster. What is Remix? Remix is a web framework built on top of the Web Fetch API, allowing for deployment on multiple platforms. It acts as a ce...

Custom routing with Remix

Create your own route convention. Use a custom glob pattern. Add layouts automatically, or prepend an optional language segment.

The Secret to Maintainable Remix Apps: Hexagonal Architecture

Ever feel like updating your Remix app's UI is a circus act? One small change, and suddenly everything's breaking? You're not alone. This fragility often comes from tightly coupled components – a change in one place triggers a domino effect throughout your code. But there's a solution: hexagonal architecture. This pattern,

How to Validate Form in Remix with clientAction by sergiodxa

When to use Route Modal in React Router by sergiodxa

Translate your Remix.run app with Lingui - Simon Depelchin

Lingui is an alternative to i18next for internationalization in Javascript project. It offers a different approach to i18n and is now available for Remix.run projects with Vite.

Remix for Next.js Developers

Snippets of code translated from Next.js to Remix. Learn Remix by example.

Replace ESLint & Prettier with Biome.js - Simon Depelchin

Learn more about Software Development

Easy Stripe Integration in your Remix.run App

In Today's episode will cover: - @Stripe Integration - Webhook Setup - Checkout Session and Payment Testing These videos are free and created for the community, support will be much appreciated! 🫶

Deploy a Remix App on Google Cloud Run

Debounce your useFetcher submissions with this custom Remix hook

Debouncing helps reduce server load. Create a custom fetcher hook that adds debounce support. Modify the type of useFetcher to support extra features.

Migrating Remix to Vite

Challenges, learnings, and scripts — still not done yet 😰