CodeVetter · Repo Unpack · System map
remix-run/remix
The repository separates portable framework packages from Node tooling, browser runtime code, example applications, and documentation generators. The `remix` distribution is generated from a canonical alias manifest rather than maintained as an independent implementation. The inspected application template starts a Node HTTP server, but routing and rendering boundaries use Web requests, responses, and streams. Storage is selected through interfaces and adapters rather than one repository-wide database.
- The root is a private ESM workspace pinned to pnpm@10.34.2 with Node >=24.3.0; its recursive scripts build, test, and typecheck workspace packages.
- The pnpm workspace includes packages, demos, documentation apps, benchmarks, CLI fixtures, the application template, and maintenance scripts.
- scripts/generate-remix.ts generates source re-exports, package exports, dependencies, copied READMEs, guides, and the documentation index from the umbrella manifest.
- The published-facing `remix` manifest exposes focused subpaths for components, auth, schema validation, databases, file storage, and middleware; its root export is types-only in the inspected source exports.
- The generated CLI executable calls runRemix(process.argv.slice(2)) and exits with its numeric result, while the reusable CLI API lives in @remix-run/cli.
- The application template runs TypeScript/JSX directly through remix/node-tsx in development and production; development uses Node watch mode, and HMR has a separate command.
- template/server.ts adapts router.fetch to Node HTTP, defaults PORT to 44100, recognizes REMIX_NODE_HMR and HMR_PROXY_PORT, and closes connections on SIGINT or SIGTERM.
- The server component renderer produces ReadableStream<Uint8Array>; the browser runtime owns document frames, scheduling, styles, module caches, and navigation listeners.
- SessionStorage defines asynchronous read(cookie) and save(session) operations; cookie storage embeds session data, whereas memory storage uses a process-local Map.
- The bookstore demo selects SQLite with foreign keys, uses an in-memory database for NODE_ENV=test, and otherwise stores its database beside SQL migrations and seed data.
- Maintenance scripts are a separate ESM workspace with Octokit, semver, YAML, and shared documentation dependencies, plus remix test and tsc validation commands.
- Repository automation includes generated comment routing, iteration, proposal review, and pull-request review workflows in addition to normal build/test workflows.