@react-router/dev 7.7.0-pre.2 → 7.7.1-pre.0

package/CHANGELOG.md

@@ -1,24 +1,16 @@
 # `@react-router/dev`
 
-## 7.7.0-pre.2
+## 7.7.1-pre.0
 
 ### Patch Changes
 
+- Update to Prettier v3 for formatting when running `react-router reveal --no-typescript` ([#14049](https://github.com/remix-run/react-router/pull/14049))
 - Updated dependencies:
-  - `react-router@7.7.0-pre.2`
-  - `@react-router/node@7.7.0-pre.2`
-  - `@react-router/serve@7.7.0-pre.2`
+  - `react-router@7.7.1-pre.0`
+  - `@react-router/node@7.7.1-pre.0`
+  - `@react-router/serve@7.7.1-pre.0`
 
-## 7.7.0-pre.1
-
-### Patch Changes
-
-- Updated dependencies:
-  - `react-router@7.7.0-pre.1`
-  - `@react-router/node@7.7.0-pre.1`
-  - `@react-router/serve@7.7.0-pre.1`
-
-## 7.7.0-pre.0
+## 7.7.0
 
 ### Patch Changes
 
@@ -30,9 +22,9 @@
 - Improve chunk error logging when a chunk cannot be found during the build ([#13799](https://github.com/remix-run/react-router/pull/13799))
 - Fix incorrectly configured `externalConditions` which had enabled `module` condition for externals and broke builds with certain packages, like Emotion. ([#13871](https://github.com/remix-run/react-router/pull/13871))
 - Updated dependencies:
-  - `react-router@7.7.0-pre.0`
-  - `@react-router/node@7.7.0-pre.0`
-  - `@react-router/serve@7.7.0-pre.0`
+  - `react-router@7.7.0`
+  - `@react-router/node@7.7.0`
+  - `@react-router/serve@7.7.0`
 
 ## 7.6.3
 
@@ -229,7 +221,6 @@
 ### Minor Changes
 
 - Added a new `react-router.config.ts` `routeDiscovery` option to configure Lazy Route Discovery behavior. ([#13451](https://github.com/remix-run/react-router/pull/13451))
-
   - By default, Lazy Route Discovery is enabled and makes manifest requests to the `/__manifest` path:
     - `routeDiscovery: { mode: "lazy", manifestPath: "/__manifest" }`
   - You can modify the manifest path used:
@@ -428,7 +419,6 @@
 ### Minor Changes
 
 - Generate a "SPA fallback" HTML file for scenarios where applications are prerendering the `/` route with `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948))
-
   - If you specify `ssr:false` without a `prerender` config, this is considered "SPA Mode" and the generated `index.html` file will only render down to the root route and will be able to hydrate for any valid application path
   - If you specify `ssr:false` with a `prerender` config but _do not_ include the `/` path (i.e., `prerender: ['/blog/post']`), then we still generate a "SPA Mode" `index.html` file that can hydrate for any path in the application
   - However, previously if you specified `ssr:false` and included the `/` path in your `prerender` config, we would prerender the `/` route into `index.html` as a non-SPA page
@@ -438,7 +428,6 @@
     - `npx sirv-cli build/client --single __spa-fallback.html`
 
 - Allow a `loader` in the root route in SPA mode because it can be called/server-rendered at build time ([#12948](https://github.com/remix-run/react-router/pull/12948))
-
   - `Route.HydrateFallbackProps` now also receives `loaderData`
     - This will be defined so long as the `HydrateFallback` is rendering while _children_ routes are loading
     - This will be `undefined` if the `HydrateFallback` is rendering because the route has it's own hydrating `clientLoader`
@@ -483,7 +472,6 @@
 - Skip action-only resource routes when using `prerender:true` ([#13004](https://github.com/remix-run/react-router/pull/13004))
 
 - Enhance invalid export detection when using `ssr:false` ([#12948](https://github.com/remix-run/react-router/pull/12948))
-
   - `headers`/`action` are prohibited in all routes with `ssr:false` because there will be no runtime server on which to run them
   - `loader` functions are more nuanced and depend on whether a given route is prerendered
     - When using `ssr:false` without a `prerender` config, only the `root` route can have a `loader`
@@ -500,7 +488,6 @@
 - Add `future.unstable_viteEnvironmentApi` flag to enable experimental Vite Environment API support ([#12936](https://github.com/remix-run/react-router/pull/12936))
 
 - Disable Lazy Route Discovery for all `ssr:false` apps and not just "SPA Mode" because there is no runtime server to serve the search-param-configured `__manifest` requests ([#12894](https://github.com/remix-run/react-router/pull/12894))
-
   - We previously only disabled this for "SPA Mode" which is `ssr:false` and no `prerender` config but we realized it should apply to all `ssr:false` apps, including those prerendering multiple pages
   - In those `prerender` scenarios we would prerender the `/__manifest` file assuming the static file server would serve it but that makes some unneccesary assumptions about the static file server behaviors
 
@@ -573,7 +560,6 @@
 - Properly initialize `NODE_ENV` if not already set for compatibility with React 19 ([#12578](https://github.com/remix-run/react-router/pull/12578))
 
 - Remove the leftover/unused `abortDelay` prop from `ServerRouter` and update the default `entry.server.tsx` to use the new `streamTimeout` value for Single Fetch ([#12478](https://github.com/remix-run/react-router/pull/12478))
-
   - The `abortDelay` functionality was removed in v7 as it was coupled to the `defer` implementation from Remix v2, but this removal of this prop was missed
   - If you were still using this prop in your `entry.server` file, it's likely your app is not aborting streams as you would expect and you will need to adopt the new [`streamTimeout`](https://reactrouter.com/explanation/special-files#streamtimeout) value introduced with Single Fetch
 
@@ -652,14 +638,13 @@
       await writeFile(
         "build/manifest.json",
         JSON.stringify(buildManifest, null, 2),
-        "utf-8"
+        "utf-8",
       );
     },
   } satisfies Config;
   ```
 
 - Consolidate types previously duplicated across `@remix-run/router`, `@remix-run/server-runtime`, and `@remix-run/react` now that they all live in `react-router` ([#12177](https://github.com/remix-run/react-router/pull/12177))
-
   - Examples: `LoaderFunction`, `LoaderFunctionArgs`, `ActionFunction`, `ActionFunctionArgs`, `DataFunctionArgs`, `RouteManifest`, `LinksFunction`, `Route`, `EntryRoute`
   - The `RouteManifest` type used by the "remix" code is now slightly stricter because it is using the former `@remix-run/router` `RouteManifest`
     - `Record<string, Route> -> Record<string, Route | undefined>`
@@ -667,7 +652,6 @@
   - Removed `ServerRuntimeMeta*` types in favor of the `Meta*` types they were duplicated from
 
 - Update default `isbot` version to v5 and drop support for `isbot@3` ([#11770](https://github.com/remix-run/react-router/pull/11770))
-
   - If you have `isbot@4` or `isbot@5` in your `package.json`:
     - You do not need to make any changes
   - If you have `isbot@3` in your `package.json` and you have your own `entry.server.tsx` file in your repo
@@ -677,7 +661,6 @@
     - You are using the internal default entry provided by React Router v7 and you will need to upgrade to `isbot@5` in your `package.json`
 
 - Drop support for Node 18, update minimum Node vestion to 20 ([#12171](https://github.com/remix-run/react-router/pull/12171))
-
   - Remove `installGlobals()` as this should no longer be necessary
 
 - For Remix consumers migrating to React Router, Vite manifests (i.e. `.vite/manifest.json`) are now written within each build subdirectory, e.g. `build/client/.vite/manifest.json` and `build/server/.vite/manifest.json` instead of `build/.vite/client-manifest.json` and `build/.vite/server-manifest.json`. This means that the build output is now much closer to what you'd expect from a typical Vite project. ([#11573](https://github.com/remix-run/react-router/pull/11573))
@@ -715,7 +698,6 @@
   ```
 
   This initial implementation targets type inference for:
-
   - `Params` : Path parameters from your routing config in `routes.ts` including file-based routing
   - `LoaderData` : Loader data from `loader` and/or `clientLoader` within your route module
   - `ActionData` : Action data from `action` and/or `clientAction` within your route module
@@ -730,7 +712,6 @@
   ```
 
   Check out our docs for more:
-
   - [_Explanations > Type Safety_](https://reactrouter.com/dev/guides/explanation/type-safety)
   - [_How-To > Setting up type safety_](https://reactrouter.com/dev/guides/how-to/setting-up-type-safety)
 
@@ -753,7 +734,6 @@
 ### Minor Changes
 
 - New `future.unstable_singleFetch` flag ([#8773](https://github.com/remix-run/remix/pull/8773))
-
   - Naked objects returned from loaders/actions are no longer automatically converted to JSON responses. They'll be streamed as-is via `turbo-stream` so `Date`'s will become `Date` through `useLoaderData()`
   - You can return naked objects with `Promise`'s without needing to use `defer()` - including nested `Promise`'s
     - If you need to return a custom status code or custom response headers, you can still use the `defer` utility
@@ -900,11 +880,9 @@
 - Always ignore route files starting with `.` ([#8801](https://github.com/remix-run/remix/pull/8801))
 
 - Vite: Enable use of [`vite preview`](https://main.vitejs.dev/guide/static-deploy.html#deploying-a-static-site) to preview Remix SPA applications ([#8624](https://github.com/remix-run/remix/pull/8624))
-
   - In the SPA template, `npm run start` has been renamed to `npm run preview` which uses `vite preview` instead of a standalone HTTP server such as `http-server` or `serv-cli`
 
 - Vite: Remove the ability to pass `publicPath` as an option to the Remix vite plugin ([#8145](https://github.com/remix-run/remix/pull/8145))
-
   - ⚠️ **This is a breaking change for projects using the unstable Vite plugin with a `publicPath`**
   - This is already handled in Vite via the [`base`](https://vitejs.dev/guide/build.html#public-base-path) config so we now set the Remix `publicPath` from the Vite `base` config
 
@@ -933,7 +911,6 @@
 - Vite: Provide `Unstable_ServerBundlesFunction` and `Unstable_VitePluginConfig` types ([#8654](https://github.com/remix-run/remix/pull/8654))
 
 - Vite: add `--sourcemapClient` and `--sourcemapServer` flags to `remix vite:build` ([#8613](https://github.com/remix-run/remix/pull/8613))
-
   - `--sourcemapClient`
 
   - `--sourcemapClient=inline`
@@ -1160,7 +1137,7 @@
       remix({
         unstable_serverBundles: ({ branch }) => {
           const isAuthenticatedRoute = branch.some(
-            (route) => route.id === "routes/_authenticated"
+            (route) => route.id === "routes/_authenticated",
           );
 
           return isAuthenticatedRoute ? "authenticated" : "unauthenticated";
@@ -1173,7 +1150,6 @@
 ### Patch Changes
 
 - Fix issue with `isbot` v4 released on 1/1/2024 ([#8415](https://github.com/remix-run/remix/pull/8415))
-
   - `remix dev` will now add `"isbot": "^4"` to `package.json` instead of using `latest`
   - Update built-in `entry.server` files to work with both `isbot@3` and `isbot@4` for backwards-compatibility with Remix apps that have pinned `isbot` to v3
   - Templates are updated to use `isbot@4` moving forward via `create-remix`
@@ -1195,7 +1171,6 @@
 ### Patch Changes
 
 - Vite: Error messages when `.server` files are referenced by client ([#8267](https://github.com/remix-run/remix/pull/8267))
-
   - Previously, referencing a `.server` module from client code resulted in an error message like:
     - `The requested module '/app/models/answer.server.ts' does not provide an export named 'isDateType'`
   - This was confusing because `answer.server.ts` _does_ provide the `isDateType` export, but Remix was replacing `.server` modules with empty modules (`export {}`) for the client build
@@ -1272,7 +1247,6 @@
 - Add support for `clientLoader`/`clientAction`/`HydrateFallback` route exports ([RFC](https://github.com/remix-run/remix/discussions/7634)) ([#8173](https://github.com/remix-run/remix/pull/8173))
 
   Remix now supports loaders/actions that run on the client (in addition to, or instead of the loader/action that runs on the server). While we still recommend server loaders/actions for the majority of your data needs in a Remix app - these provide some levers you can pull for more advanced use-cases such as:
-
   - Leveraging a data source local to the browser (i.e., `localStorage`)
   - Managing a client-side cache of server data (like `IndexedDB`)
   - Bypassing the Remix server in a BFF setup and hitting your API directly from the browser
@@ -1381,7 +1355,6 @@
 - Add `@remix-run/node` to Vite's `optimizeDeps.include` array ([#8177](https://github.com/remix-run/remix/pull/8177))
 
 - Improve Vite plugin performance ([#8121](https://github.com/remix-run/remix/pull/8121))
-
   - Parallelize detection of route module exports
   - Disable `server.preTransformRequests` in Vite child compiler since it's only used to process route modules
 
@@ -1551,7 +1524,6 @@
   - Additionally, all runtimes (including non-Node runtimes) can use `build.mode` to determine if HMR should be performed
 - Support `bun` package manager ([#7074](https://github.com/remix-run/remix/pull/7074))
 - The `serverNodeBuiltinsPolyfill` option (along with the newly added `browserNodeBuiltinsPolyfill`) now supports defining global polyfills in addition to module polyfills ([#7269](https://github.com/remix-run/remix/pull/7269))
-
   - For example, to polyfill Node's `Buffer` global:
 
     ```js
@@ -1574,7 +1546,6 @@
 - Fix importing of PNGs, SVGs, and other assets from packages in `node_modules` ([#6813](https://github.com/remix-run/remix/pull/6813), [#7182](https://github.com/remix-run/remix/pull/7182))
 
 - Decouple the `@remix-run/dev` package from the contents of the `@remix-run/css-bundle` package. ([#6982](https://github.com/remix-run/remix/pull/6982))
-
   - The contents of the `@remix-run/css-bundle` package are now entirely managed by the Remix compiler
   - Even though it's still recommended that your Remix dependencies all share the same version, this change ensures that there are no runtime errors when upgrading `@remix-run/dev` without upgrading `@remix-run/css-bundle`
 
@@ -1583,7 +1554,6 @@
 - Stop `remix dev` when `esbuild` is not running ([#7158](https://github.com/remix-run/remix/pull/7158))
 
 - Do not interpret JSX in `.ts` files ([#7306](https://github.com/remix-run/remix/pull/7306))
-
   - While JSX is supported in `.js` files for compatibility with existing apps and libraries,
     `.ts` files should not contain JSX. By not interpreting `.ts` files as JSX, `.ts` files
     can contain single-argument type generics without needing a comma to disambiguate from JSX:
@@ -1617,7 +1587,6 @@
 - Kill app server when remix dev terminates ([#7280](https://github.com/remix-run/remix/pull/7280))
 
 - Support dependencies that import polyfill packages for Node built-ins via a trailing slash (e.g. importing the `buffer` package with `var Buffer = require('buffer/').Buffer` as recommended in their README) ([#7198](https://github.com/remix-run/remix/pull/7198))
-
   - These imports were previously marked as external
   - This meant that they were left as dynamic imports in the client bundle and would throw a runtime error in the browser (e.g. `Dynamic require of "buffer/" is not supported`)
 
@@ -1626,14 +1595,12 @@
 - Restart dev server when Remix config changes ([#7269](https://github.com/remix-run/remix/pull/7269))
 
 - Remove outdated ESM import warnings ([#6916](https://github.com/remix-run/remix/pull/6916))
-
   - Most of the time these warnings were false positives.
   - Instead, we now rely on built-in Node warnings for ESM imports.
 
 - Do not trigger rebuilds when `.DS_Store` changes ([#7172](https://github.com/remix-run/remix/pull/7172))
 
 - Remove warnings for stabilized flags: ([#6905](https://github.com/remix-run/remix/pull/6905))
-
   - `unstable_cssSideEffectImports`
   - `unstable_cssModules`
   - `unstable_vanillaExtract`
@@ -1683,7 +1650,6 @@
 - Output esbuild metafiles for bundle analysis ([#6772](https://github.com/remix-run/remix/pull/6772))
 
   Written to server build directory (`build/` by default):
-
   - `metafile.css.json`
   - `metafile.js.json` (browser JS)
   - `metafile.server.json` (server JS)
@@ -1781,7 +1747,6 @@
 - built-in tls support ([#6483](https://github.com/remix-run/remix/pull/6483))
 
   New options:
-
   - `--tls-key` / `tlsKey`: TLS key
   - `--tls-cert` / `tlsCert`: TLS Certificate
 
@@ -1852,7 +1817,7 @@
       key: fs.readFileSync("key.pem"),
       cert: fs.readFileSync("cert.pem"),
     },
-    app
+    app,
   );
 
   appServer.listen(3000, () => {
@@ -1915,7 +1880,6 @@
 - restore color for app server output ([#6485](https://github.com/remix-run/remix/pull/6485))
 
 - Fix route ranking bug with pathless layout route next to a sibling index route ([#4421](https://github.com/remix-run/remix/pull/4421))
-
   - Under the hood this is done by removing the trailing slash from all generated `path` values since the number of slash-delimited segments counts towards route ranking so the trailing slash incorrectly increases the score for routes
 
 - Support sibling pathless layout routes by removing pathless layout routes from the unique route path checks in conventional route generation since they inherently trigger duplicate paths ([#4421](https://github.com/remix-run/remix/pull/4421))
@@ -2053,7 +2017,6 @@
   ```
 
   The dev server will:
-
   - force `NODE_ENV=development` and warn you if it was previously set to something else
   - rebuild your app whenever your Remix app code changes
   - restart your app server whenever rebuilds succeed
@@ -2183,7 +2146,6 @@
 - Added deprecation warning for `v2_normalizeFormMethod` ([#5863](https://github.com/remix-run/remix/pull/5863))
 
 - Added a new `future.v2_normalizeFormMethod` flag to normalize the exposed `useNavigation().formMethod` as an uppercase HTTP method to align with the previous `useTransition` behavior as well as the `fetch()` behavior of normalizing to uppercase HTTP methods. ([#5815](https://github.com/remix-run/remix/pull/5815))
-
   - When `future.v2_normalizeFormMethod === false`,
     - `useNavigation().formMethod` is lowercase
     - `useFetcher().formMethod` is uppercase
@@ -2258,7 +2220,6 @@
 ### Patch Changes
 
 - Fixes flat route inconsistencies where `route.{ext}` wasn't always being treated like `index.{ext}` when used in a folder ([#5459](https://github.com/remix-run/remix/pull/5459))
-
   - Route conflict no longer throw errors and instead display a helpful warning that we're using the first one we found.
 
     ```log

package/dist/cli/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 /**
- * @react-router/dev v7.7.0-pre.2
+ * @react-router/dev v7.7.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *
@@ -2066,7 +2066,7 @@ var babel = __toESM(require("@babel/core"));
 var import_plugin_syntax_jsx = __toESM(require("@babel/plugin-syntax-jsx"));
 var import_preset_typescript = __toESM(require("@babel/preset-typescript"));
 var import_prettier = __toESM(require("prettier"));
-function transpile(tsx, options = {}) {
+async function transpile(tsx, options = {}) {
   let mjs = babel.transformSync(tsx, {
     compact: false,
     cwd: options.cwd,
@@ -2076,7 +2076,7 @@ function transpile(tsx, options = {}) {
     retainLines: true
   });
   if (!mjs || !mjs.code) throw new Error("Could not parse TypeScript");
-  return import_prettier.default.format(mjs.code, { parser: "babel" });
+  return await import_prettier.default.format(mjs.code, { parser: "babel" });
 }
 
 // cli/commands.ts
@@ -2174,7 +2174,7 @@ async function generateEntry(entry, rootDirectory, flags = {}) {
   let outputEntry = `${entry}.${outputExtension}`;
   let outputFile = path7.resolve(appDirectory, outputEntry);
   if (!useTypeScript) {
-    let javascript = transpile(contents, {
+    let javascript = await transpile(contents, {
       cwd: rootDirectory,
       filename: isServerEntry ? defaultEntryServer : defaultEntryClient
     });

package/dist/config/defaults/entry.client.tsx

@@ -7,6 +7,6 @@ startTransition(() => {
     document,
     <StrictMode>
       <HydratedRouter />
-    </StrictMode>
+    </StrictMode>,
   );
 });

package/dist/config/defaults/entry.server.node.tsx

@@ -14,7 +14,7 @@ export default function handleRequest(
   responseStatusCode: number,
   responseHeaders: Headers,
   routerContext: EntryContext,
-  loadContext: AppLoadContext
+  loadContext: AppLoadContext,
   // If you have middleware enabled:
   // loadContext: unstable_RouterContextProvider
 ) {
@@ -43,7 +43,7 @@ export default function handleRequest(
             new Response(stream, {
               headers: responseHeaders,
               status: responseStatusCode,
-            })
+            }),
           );
 
           pipe(body);
@@ -60,7 +60,7 @@ export default function handleRequest(
             console.error(error);
           }
         },
-      }
+      },
     );
 
     // Abort the rendering stream after the `streamTimeout` so it has time to

package/dist/config.js

@@ -1,5 +1,5 @@
 /**
- * @react-router/dev v7.7.0-pre.2
+ * @react-router/dev v7.7.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *

package/dist/routes.js

@@ -1,5 +1,5 @@
 /**
- * @react-router/dev v7.7.0-pre.2
+ * @react-router/dev v7.7.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *

package/dist/static/{refresh-utils.cjs → refresh-utils.mjs}

@@ -20,7 +20,7 @@ const enqueueUpdate = debounce(async () => {
       let imported = window.__reactRouterRouteModuleUpdates.get(route.id);
       if (!imported) {
         throw Error(
-          `[react-router:hmr] No module update found for route ${route.id}`
+          `[react-router:hmr] No module update found for route ${route.id}`,
         );
       }
       let routeModule = {
@@ -28,16 +28,16 @@ const enqueueUpdate = debounce(async () => {
         // react-refresh takes care of updating these in-place,
         // if we don't preserve existing values we'll loose state.
         default: imported.default
-          ? window.__reactRouterRouteModules[route.id]?.default ??
-            imported.default
+          ? (window.__reactRouterRouteModules[route.id]?.default ??
+            imported.default)
           : imported.default,
         ErrorBoundary: imported.ErrorBoundary
-          ? window.__reactRouterRouteModules[route.id]?.ErrorBoundary ??
-            imported.ErrorBoundary
+          ? (window.__reactRouterRouteModules[route.id]?.ErrorBoundary ??
+            imported.ErrorBoundary)
           : imported.ErrorBoundary,
         HydrateFallback: imported.HydrateFallback
-          ? window.__reactRouterRouteModules[route.id]?.HydrateFallback ??
-            imported.HydrateFallback
+          ? (window.__reactRouterRouteModules[route.id]?.HydrateFallback ??
+            imported.HydrateFallback)
           : imported.HydrateFallback,
       };
       window.__reactRouterRouteModules[route.id] = routeModule;
@@ -49,9 +49,9 @@ const enqueueUpdate = debounce(async () => {
           (route) =>
             route.hasLoader ||
             route.hasClientLoader ||
-            route.hasClientMiddleware
+            route.hasClientMiddleware,
         )
-        .map((route) => route.id)
+        .map((route) => route.id),
     );
 
     let routes = __reactRouterDataRouter.createRoutesForHMR(
@@ -59,7 +59,7 @@ const enqueueUpdate = debounce(async () => {
       manifest.routes,
       window.__reactRouterRouteModules,
       window.__reactRouterContext.ssr,
-      window.__reactRouterContext.isSpaMode
+      window.__reactRouterContext.isSpaMode,
     );
     __reactRouterDataRouter._internalSetRoutes(routes);
     routeUpdates.clear();
@@ -99,12 +99,12 @@ function validateRefreshBoundaryAndEnqueueUpdate(
   prevExports,
   nextExports,
   // non-component exports that are handled by the framework (e.g. `meta` and `links` for route modules)
-  acceptExports = []
+  acceptExports = [],
 ) {
   if (
     !predicateOnExport(
       prevExports,
-      (key) => key in nextExports || acceptExports.includes(key)
+      (key) => key in nextExports || acceptExports.includes(key),
     )
   ) {
     return "Could not Fast Refresh (export removed)";
@@ -112,7 +112,7 @@ function validateRefreshBoundaryAndEnqueueUpdate(
   if (
     !predicateOnExport(
       nextExports,
-      (key) => key in prevExports || acceptExports.includes(key)
+      (key) => key in prevExports || acceptExports.includes(key),
     )
   ) {
     return "Could not Fast Refresh (new export)";
@@ -129,7 +129,7 @@ function validateRefreshBoundaryAndEnqueueUpdate(
       if (exports.isLikelyComponentType(value)) return true;
       // Unchanged exports are implicitly handled
       return prevExports[key] === nextExports[key];
-    }
+    },
   );
   if (hasExports && allExportsAreHandledOrUnchanged) {
     enqueueUpdate();

package/dist/vite/cloudflare.js

@@ -1,5 +1,5 @@
 /**
- * @react-router/dev v7.7.0-pre.2
+ * @react-router/dev v7.7.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *

package/dist/vite.js

@@ -1,5 +1,5 @@
 /**
- * @react-router/dev v7.7.0-pre.2
+ * @react-router/dev v7.7.1-pre.0
  *
  * Copyright (c) Remix Software Inc.
  *
@@ -3819,7 +3819,7 @@ var reactRouterVitePlugin = () => {
         return [
           "const exports = {}",
           await (0, import_promises2.readFile)(reactRefreshRuntimePath, "utf8"),
-          await (0, import_promises2.readFile)(require.resolve("./static/refresh-utils.cjs"), "utf8"),
+          await (0, import_promises2.readFile)(require.resolve("./static/refresh-utils.mjs"), "utf8"),
           "export default exports"
         ].join("\n");
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@react-router/dev",
-  "version": "7.7.0-pre.2",
+  "version": "7.7.1-pre.0",
   "description": "Dev tools and CLI for React Router",
   "homepage": "https://reactrouter.com",
   "bugs": {
@@ -79,14 +79,14 @@
     "lodash": "^4.17.21",
     "pathe": "^1.1.2",
     "picocolors": "^1.1.1",
-    "prettier": "^2.7.1",
+    "prettier": "^3.6.2",
     "react-refresh": "^0.14.0",
     "semver": "^7.3.7",
     "set-cookie-parser": "^2.6.0",
     "tinyglobby": "^0.2.14",
     "valibot": "^0.41.0",
     "vite-node": "^3.2.2",
-    "@react-router/node": "7.7.0-pre.2"
+    "@react-router/node": "7.7.1-pre.0"
   },
   "devDependencies": {
     "@types/babel__core": "^7.20.5",
@@ -98,7 +98,6 @@
     "@types/lodash": "^4.14.182",
     "@types/node": "^20.0.0",
     "@types/npmcli__package-json": "^4.0.0",
-    "@types/prettier": "^2.7.3",
     "@types/set-cookie-parser": "^2.4.1",
     "@types/semver": "^7.7.0",
     "esbuild-register": "^3.6.0",
@@ -110,15 +109,15 @@
     "vite": "^6.1.0",
     "wireit": "0.14.9",
     "wrangler": "^4.23.0",
-    "@react-router/serve": "7.7.0-pre.2",
-    "react-router": "^7.7.0-pre.2"
+    "@react-router/serve": "7.7.1-pre.0",
+    "react-router": "^7.7.1-pre.0"
   },
   "peerDependencies": {
     "typescript": "^5.1.0",
     "vite": "^5.1.0 || ^6.0.0 || ^7.0.0",
     "wrangler": "^3.28.2 || ^4.0.0",
-    "@react-router/serve": "^7.7.0-pre.2",
-    "react-router": "^7.7.0-pre.2"
+    "@react-router/serve": "^7.7.1-pre.0",
+    "react-router": "^7.7.1-pre.0"
   },
   "peerDependenciesMeta": {
     "@react-router/serve": {