Merge branch 'dev' into issue-9844_fix-injection-of-inline-and-raw-cs…

…s-files

.changeset/hungry-experts-suffer.md

@@ -0,0 +1,5 @@
+---
+"@remix-run/dev": patch
+---
+
+Properly abort `request.signal` during `vite dev` when the node response is closed

.changeset/tender-pears-confess.md

@@ -0,0 +1,8 @@
+---
+"@remix-run/cloudflare": patch
+"@remix-run/deno": patch
+"@remix-run/node": patch
+"@remix-run/server-runtime": patch
+---
+
+Single Fetch: Re-export `interface Future` through `@remix-run/node`/`@remix-run/cloudflare`/`@remix-run/deno` packages so that `pnpm` doesn't complain about `@remix-run/server-runtime` not being a dependency

contributors.yml

@@ -367,6 +367,7 @@
 - kishanhitk
 - kiyadotdev
 - klauspaiva
+- klirium
 - knowler
 - konradkalemba
 - krolebord
@@ -485,6 +486,7 @@
 - n8agrin
 - na2hiro
 - nareshbhatia
+- nauvalazhar
 - naveed-fida
 - navid-kalaei
 - nexxeln
@@ -504,6 +506,7 @@
 - niwsa
 - nobeeakon
 - nordiauwu
+- nornagon
 - not-ivy
 - npapagna
 - nrako
@@ -547,6 +550,7 @@
 - remix-run-bot
 - richardhunghhw
 - riencoertjens
+- risv1
 - rkulinski
 - rlfarman
 - roachjc

docs/file-conventions/routes.md

@@ -246,7 +246,7 @@ Sometimes you want to share a layout with a group of routes without adding any p
 | `/`                        | `app/routes/_index.tsx`         | `app/root.tsx`            |
 | `/login`                   | `app/routes/_auth.login.tsx`    | `app/routes/_auth.tsx`    |
 | `/register`                | `app/routes/_auth.register.tsx` | `app/routes/_auth.tsx`    |
-| `/concerts`                | `app/routes/concerts.tsx`       | `app/routes/concerts.tsx` |
+| `/concerts`                | `app/routes/concerts.tsx`       | `app/root.tsx`            |
 | `/concerts/salt-lake-city` | `app/routes/concerts.$city.tsx` | `app/routes/concerts.tsx` |
 
 Think of the `_leading` underscore as a blanket you're pulling over the filename, hiding the filename from the URL.

docs/guides/dependency-optimization.md

@@ -0,0 +1,68 @@
+---
+title: Dependency optimization
+---
+
+<docs-info>This feature only affects development. It does not impact production builds.</docs-info>
+
+# Dependency optimization
+
+Remix introduced automatic dependency optimization in development behind the `future.unstable_optimizeDeps` [Future Flag][future-flags].
+This allows you to opt-into this behavior which will become the default in the next major version of Remix - a.k.a. React Router v7 ([1][rr-v7], [2][rr-v7-2]).
+
+In development, Vite aims to [prebundle dependencies][prebundle-dependencies] so that it can efficiently serve up those dependencies on-demand.
+To do this, Vite needs to know where to start crawling your app's module graph to look for dependencies.
+
+Previously, Remix did not inform Vite to start dependency detection at route modules nor at the client entry.
+That meant that in development, Vite would encounter new dependencies as you navigated around in your app resulting in `504 Outdated Dependency` errors.
+Consequently, the development experience could feel janky at times since those errors could cause HMR to break or link navigations to be aborted.
+Navigation could also feel sluggish as processing dependencies interactively could sometimes be slow.
+
+For more information, see [Vite's Dep Optimization Options][vite-s-dep-optimization-options].
+
+## Troubleshooting
+
+### `Failed to resolve entry for package`
+
+```txt
+✘ [ERROR] Failed to resolve entry for package "<package>". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-pre-bundle]
+```
+
+This is usually caused by a misconfigured dependency.
+You use [publint][publint] to check if the offending package is misconfigured.
+To fix the issue, you'll need to use `npm why` or `pnpm why` to determine which of your direct dependencies to add to `optimizeDeps.exclude`.
+
+For example, let's say your app is running into this error:
+
+```txt
+✘ [ERROR] Failed to resolve entry for package "jimp". The package may have incorrect main/module/exports specified in its package.json. [plugin vite:dep-pre-bundle]
+```
+
+Sure enough, `publint` reports that the [`jimp` package is misconfigured][jimp-package-is-misconfigured].
+Then, you determine that `jimp` is an indirect dependency being pulled in by your `svg2img` direct dependency:
+
+```sh
+❯ npm why jimp
+jimp@0.16.13
+node_modules/jimp
+  jimp@"^0.16.1" from svg2img@1.0.0-beta.2
+  node_modules/svg2img
+    svg2img@"^1.0.0-beta.2" from the root project
+```
+
+Finally, you add `svg2img` to `optimizeDeps.exclude`, which should fix the issue:
+
+```ts filename=vite.config.ts
+export default defineConfig({
+  optimizeDeps: {
+    exclude: ["svg2img"],
+  },
+});
+```
+
+[future-flags]: ../guides/api-development-strategy
+[rr-v7]: https://remix.run/blog/merging-remix-and-react-router
+[rr-v7-2]: https://remix.run/blog/incremental-path-to-react-19
+[prebundle-dependencies]: https://vitejs.dev/guide/dep-pre-bundling.html
+[vite-s-dep-optimization-options]: https://vitejs.dev/config/dep-optimization-options#dep-optimization-options
+[publint]: https://publint.dev
+[jimp-package-is-misconfigured]: https://publint.dev/jimp@0.22.12