A Remix v2 starter in TypeScript on Vite, with React 18 server-side rendering, for developers who want loaders and resource routes on a Node.js server. It includes Home and About pages, a GET /api/health resource route, Tailwind CSS, ESLint and Vitest.
by Light CloudFull-stack


For each request Remix runs the loaders of every matching route on the server, renders the page with their data and streams the HTML, then React hydrates it in the browser. Environment variables are read only on the server, in loaders, and passed to the page as loader data, which keeps secrets out of the bundle. The three v3 future flags already on make a later move to React Router v7 shorter. Most people first add routes in app/routes/ and actions for forms. Deploying runs npm run build, then npm start (remix-serve) in a container that listens on PORT.
Create a file in app/routes/: contact.tsx becomes /contact, and dots make path segments, so blog.first-post.tsx becomes /blog/first-post. Add a NavLink to it in app/components/SiteHeader.tsx.
Add a resource route: a file in app/routes/ that exports a loader for GET or an action for POST, PUT and DELETE, and no default component. api.health.ts is the example.
Remix v2 continues as React Router v7, and the upgrade path is to turn on the remaining v3 future flags and then switch packages. This template already has three of those flags on in vite.config.ts.
Read process.env.NAME in a loader or action, which run on the server, and return what the page needs, as the root loader does with SITE_NAME. npm run dev loads .env; npm start reads the real environment.
Yes. It has no Light Cloud code in it: any host with Node.js 20 or later runs it with npm ci, npm run build and npm start.