Welcome to Remix 3!

This is the source repository for Remix 3. It is under active development.

We published a blog post earlier this year with some of our thoughts around Remix 3. It explains our philosophy for web development and why we think the time is right for something new. When working on Remix 3, we follow these principles:

1. Model-First Development. AI fundamentally shifts the human-computer interaction model for both user experience and developer workflows. Optimize the source code, documentation, tooling, and abstractions for LLMs. Additionally, develop abstractions for applications to use models in the product itself, not just as a tool to develop it.
2. Build on Web APIs. Sharing abstractions across the stack greatly reduces the amount of context switching, both for humans and machines. Build on the foundation of Web APIs and JavaScript because it is the only full stack ecosystem.
3. Religiously Runtime. Designing for bundlers/compilers/typegen (and any pre-runtime static analysis) leads to poor API design that eventually pollutes the entire system. All packages must be designed with no expectation of static analysis and all tests must run without bundling. Because browsers are involved, --import loaders for simple transformations like TypeScript and JSX are permissible.
4. Avoid Dependencies. Dependencies lock you into somebody else's roadmap. Choose them wisely, wrap them completely, and expect to replace most of them with our own package eventually. The goal is zero.
5. Demand Composition. Abstractions should be single-purpose and replaceable. A composable abstraction is easy to add and remove from an existing program. Every package must be useful and documented independent of any other context. New features should first be attempted as a new package. If impossible, attempt to break up the existing package to make it more composable. However, tightly coupled modules that almost always change together in both directions should be moved to the same package.
6. Distribute Cohesively. Extremely composable ecosystems are difficult to learn and use. Remix will be distributed as a single remix package for both distribution and documentation.

Goals

Although we recommend the remix package for ease of use, all packages that make up Remix should be usable standalone as well. This forces us to consider package boundaries and helps us define public interfaces that are portable and interoperable.

Each package in Remix:

• Has a single responsibility
• Prioritizes web standards to ensure maximum interoperability and portability across JavaScript runtimes
• Augments standards unobtrusively where they are missing or incomplete, minimizing incompatibility risks

This means Remix code is portable by default. Remix packages work seamlessly across Node.js, Bun, Deno, Cloudflare Workers, and other environments.

We leverage server-side web APIs when they are available:

• The Web Streams API instead of node:stream
• Uint8Array instead of Node.js Buffers
• The Web Crypto API instead of node:crypto
• Blob and File instead of some bespoke runtime-specific API

The benefit is code that's not just reusable, but future-proof.

Packages

We currently publish the following packages:

• async-context-middleware: Middleware for storing request context in AsyncLocalStorage
• component: UI components for Remix
• compression-middleware: Middleware for compressing HTTP responses
• cop-middleware: Middleware for tokenless cross-origin protection in Fetch API servers
• cors-middleware: Middleware for handling CORS in Fetch API servers
• csrf-middleware: Middleware for CSRF protection in Fetch API servers
• cookie: A toolkit for working with cookies in JavaScript
• data-schema: Tiny, standards-aligned schema validation
• data-table: A typed, relational query toolkit for Remix
• data-table-mysql: MySQL adapter for remix/data-table
• data-table-postgres: PostgreSQL adapter for remix/data-table
• data-table-sqlite: SQLite adapter for remix/data-table
• fetch-proxy: An HTTP proxy for the web Fetch API
• fetch-router: A minimal, composable router for the web Fetch API
• file-storage: Key/value storage for JavaScript File objects
• file-storage-s3: S3 backend for remix/file-storage
• form-data-middleware: Middleware for parsing FormData from request bodies
• form-data-parser: A request.formData() wrapper with streaming file upload handling
• fs: Filesystem utilities using the Web File API
• headers: A toolkit for working with HTTP headers in JavaScript
• html-template: HTML template tag with auto-escaping for JavaScript
• lazy-file: Lazy, streaming files for JavaScript
• logger-middleware: Middleware for logging HTTP requests and responses
• method-override-middleware: Middleware for overriding HTTP request methods from form data
• mime: Utilities for working with MIME types
• multipart-parser: A fast, efficient parser for multipart streams in any JavaScript environment
• node-fetch-server: Build servers for Node.js using the web fetch API
• remix: Remix Web Framework
• response: Response helpers for the web Fetch API
• route-pattern: Match and generate URLs with strong typing
• session: Session management for JavaScript
• session-middleware: Middleware for managing sessions with cookie-based storage
• session-storage-memcache: Memcache session storage for remix/session
• session-storage-redis: Redis session storage for remix/session
• static-middleware: Middleware for serving static files from the filesystem
• tar-parser: A fast, efficient parser for tar streams in any JavaScript environment

Installation

To try the current Remix alpha, install the next dist-tag:

npm install remix@next

If you want to play around with the bleeding edge, we also build the latest main branch into a preview/main branch which can be installed directly with pnpm (version 9+):

pnpm install "remix-run/remix#preview/main&path:packages/remix"

# Or, just install a single package
pnpm install "remix-run/remix#preview/main&path:packages/fetch-router"

Contributing

We welcome contributions! If you'd like to contribute, please feel free to open an issue or submit a pull request. See CONTRIBUTING for more information.

License

See LICENSE