Remove Remix pages guide (#25263)

dario-piotrowicz · web-flow · commit 668c82653c2a · 2025-09-26T15:28:21.000+01:00
diff --git a/src/content/docs/pages/framework-guides/deploy-a-remix-site.mdx b/src/content/docs/pages/framework-guides/deploy-a-remix-site.mdx
@@ -11,180 +11,8 @@ import {
 	WranglerConfig,
 } from "~/components";
 
-[Remix](https://remix.run/) is a framework that is focused on fully utilizing the power of the web. Like Cloudflare Workers, it uses modern JavaScript APIs, and it places emphasis on web fundamentals such as meaningful HTTP status codes, caching and optimizing for both usability and performance.
+[Remix](https://remix.run/) is a framework that focused on web standard. The framework is no longer recommended for new projects by the authors and its successor React Router should be used instead.
 
-In this guide, you will create a new Remix application and deploy to Cloudflare Pages.
+To start a new React Router project please refer to the [React Router Workers guide](/workers/framework-guides/web-apps/react-router).
 
-## Setting up a new project
-
-Use the [`create-cloudflare`](https://www.npmjs.com/package/create-cloudflare) CLI (C3) to set up a new project. C3 will create a new project directory, initiate Remix's official setup tool, and provide the option to deploy instantly.
-
-To use `create-cloudflare` to create a new Remix project, run the following command:
-
-<PackageManagers
-	type="create"
-	pkg="cloudflare@latest"
-	args="my-remix-app --framework=remix --platform=pages"
-/>
-
-`create-cloudflare` will install additional dependencies, including the [Wrangler](/workers/wrangler/install-and-update/#check-your-wrangler-version) CLI and any necessary adapters, and ask you setup questions.
-
-:::caution[Before you deploy]
-
-Your Remix project will include a `functions/[[path]].ts` file. The `[[path]]` filename indicates that this file will handle requests to all incoming URLs. Refer to [Path segments](/pages/functions/routing/#dynamic-routes) to learn more.
-
-The `functions/[[path]].ts` will not function as expected if you attempt to deploy your site before running `remix vite:build`.
-:::
-
-After setting up your project, change the directory and render your project by running the following command:
-
-```sh
-# choose Cloudflare Pages
-cd my-remix-app
-npm run dev
-```
-
-<Render file="tutorials-before-you-start" product="pages" />
-
-<Render
-	file="framework-guides/create-github-repository_no_init"
-	product="pages"
-/>
-
-## Deploy with Cloudflare Pages
-
-<Render file="deploy-via-c3" product="pages" params={{ name: "Remix" }} />
-
-### Deploy via the Cloudflare dashboard
-
-<Render
-	file="framework-guides/learn-more"
-	product="pages"
-	params={{ name: "Remix" }}
-/>
-
-<PagesBuildPreset framework="remix" />
-
-After configuring your site, you can begin your first deploy. You should see Cloudflare Pages installing `npm`, your project dependencies, and building your site before deploying it.
-
-:::note
-
-For the complete guide to deploying your first site to Cloudflare Pages, refer to the [Get started guide](/pages/get-started/).
-
-:::
-
-After deploying your site, you will receive a unique subdomain for your project on `*.pages.dev`.
-Every time you commit new code to your Remix site, Cloudflare Pages will automatically rebuild your project and deploy it. You will also get access to [preview deployments](/pages/configuration/preview-deployments/) on new pull requests, so you can preview how changes look to your site before deploying them to production.
-
-### Deploy via the Wrangler CLI
-
-If you use [`create-cloudflare`(C3)](https://www.npmjs.com/package/create-cloudflare) to create your new Remix project, C3 will automatically scaffold your project with [`wrangler`](/workers/wrangler/). To deploy your project, run the following command:
-
-```sh
-npm run deploy
-```
-
-## Create and add a binding to your Remix application
-
-To add a binding to your Remix application, refer to [Bindings](/pages/functions/bindings/).
-A [binding](/pages/functions/bindings/) allows your application to interact with Cloudflare developer products, such as [KV namespaces](/kv/concepts/how-kv-works/), [Durable Objects](/durable-objects/), [R2 storage buckets](/r2/), and [D1 databases](/d1/).
-
-### Binding resources in local development
-
-Remix uses Wrangler's [`getPlatformProxy`](/workers/wrangler/api/#getplatformproxy) to simulate the Cloudflare environment locally. You configure `getPlatformProxy` in your project's `vite.config.ts` file via [`cloudflareDevProxyVitePlugin`](https://remix.run/docs/en/main/future/vite#cloudflare-proxy).
-
-To bind resources in local development, you need to configure the bindings in the Wrangler file. Refer to [Bindings](/workers/wrangler/configuration/#bindings) to learn more.
-
-Once you have configured the bindings in the Wrangler file, the proxies are then available within `context.cloudflare` in your `loader` or `action` functions:
-
-```typescript
-export const loader = ({ context }: LoaderFunctionArgs) => {
-	const { env, cf, ctx } = context.cloudflare;
-	env.MY_BINDING; // Access bound resources here
-	// ... more loader code here...
-};
-```
-
-:::note[Correcting the env type]
-
-You may have noticed that `context.cloudflare.env` is not typed correctly when you add additional bindings in the [Wrangler configuration file](/workers/wrangler/configuration/).
-
-To fix this, run `npm run typegen` to generate the missing types. This will update the `Env` interface defined in `worker-configuration.d.ts`.
-After running the command, you can access the bindings in your `loader` or `action` using `context.cloudflare.env` as shown above.
-:::
-
-### Binding resources in production
-
-To bind resources in production, you need to configure the bindings in the Cloudflare dashboard. Refer to the [Bindings](/pages/functions/bindings/) documentation to learn more.
-
-Once you have configured the bindings in the Cloudflare dashboard, the proxies are then available within `context.cloudflare.env` in your `loader` or `action` functions as shown [above](#binding-resources-in-local-development).
-
-## Example: Access your D1 database in a Remix application
-
-As an example, you will bind and query a D1 database in a Remix application.
-
-1. Create a D1 database. Refer to the [D1 documentation](/d1/) to learn more.
-2. Configure bindings for your D1 database in the Wrangler file:
-
-<WranglerConfig>
-
-```toml
-[[ d1_databases ]]
-binding = "DB"
-database_name = "<YOUR_DATABASE_NAME>"
-database_id = "<YOUR_DATABASE_ID>"
-```
-
-</WranglerConfig>
-
-3. Run `npm run typegen` to generate TypeScript types for your bindings.
-
-```sh
-npm run typegen
-```
-
-```sh output
-> typegen
-> wrangler types
-
- ⛅️ wrangler 3.48.0
--------------------
-interface Env {
-	DB: D1Database;
-}
-```
-
-4. Access the D1 database in your `loader` function:
-
-```typescript
-import type { LoaderFunction } from "@remix-run/cloudflare";
-import { json } from "@remix-run/cloudflare";
-import { useLoaderData } from "@remix-run/react";
-
-export const loader: LoaderFunction = async ({ context, params }) => {
-  const { env, cf, ctx } = context.cloudflare;
-  let { results } = await env.DB.prepare(
-    "SELECT * FROM products where id = ?1"
-  ).bind(params.productId).run();
-  return json(results);
-};
-
-export default function Index() {
-  const results = useLoaderData<typeof loader>();
-  return (
-    <div>
-      <h1>Welcome to Remix</h1>
-      <div>
-        A value from D1:
-        <pre>{JSON.stringify(results)}</pre>
-      </div>
-    </div>
-  );
-}
-```
-
-<Render
-	file="framework-guides/learn-more"
-	product="pages"
-	params={{ one: "Remix" }}
-/>
+And if you have an existing Remix application consider migrating it to React Router as described in the [official Remix upgrade documentation](https://reactrouter.com/upgrading/remix).
