CodeVetter · Repo Unpack · Feature catalog
remix-run/remix
The primary users are application developers consuming framework APIs and CLI commands. Features include routing, server and browser UI, assets, authentication, database management, storage, and testing. The bookstore and social-auth applications expose concrete examples of these capabilities. This catalog covers inspected public surfaces and documented package families; it is not an exhaustive enumeration of every export or demo screen.
- runRemix dispatches new, completion, assets, doctor, db, routes, test, version, and help commands, including --help and --version aliases.
- `remix new <target-dir>` scaffolds an application and accepts --app-name and --force.
- `remix assets` lists browser-reachable assets; `remix assets inspect <url-or-file>` reports status, URL, file path, and matching denial information.
- Database CLI help exposes wipe, migrate, rollback, status, seed, and reset, with migration targeting, rollback dry-run, connection environment selection, and force flags for destructive operations.
- Routing supports method-specific registration, controller mapping, mounted route installers, automatic HEAD fallback from GET, and 405 responses with Allow headers.
- The template exposes a home page and /assets/*path; its home controller returns component-rendered HTML and its asset controller falls back to a 404 response.
- render middleware provides streaming component HTML, nested frame resolution, and asset-backed client-entry metadata; the browser runtime exposes ready(), flush(), dispose(), and frame handles.
- Template assets support development source maps, watching, optional component HMR, production minification, file allowlists, package allowlists, and test-file denial.
- The auth public entrypoint exports credentials authentication, OAuth/OIDC lifecycle helpers, and provider factories for Auth0, Facebook, GitHub, Google, Microsoft, OIDC, Okta, and X.
- The bookstore route map includes catalog browsing by genre and slug, search, contact forms, login and registration, password recovery, account settings, order views, cart APIs, checkout, and administrative resources.
- The social-auth GitHub controller redirects into external login, resolves callback identities into persistent users/accounts, stores authentication state, and reports configuration or login failures through session flash messages.
- Documented package families also provide schema validation, MySQL/Postgres/SQLite queries, S3 file storage, multipart uploads, HTTP headers, compression, CORS/CSRF protection, and headless UI primitives.