Vite 8 build warning, please use oxc instead

[ReaJason]

❯ nr build
$ react-router build
10:55:23 AM [vite] warning: `esbuild` option was specified by "react-router" plugin. This option is deprecated, please use `oxc` instead.
10:55:24 AM [vite] warning: `esbuild` option was specified by "react-router" plugin. This option is deprecated, please use `oxc` instead. (x2)
10:55:24 AM [vite] warning: `esbuild` option was specified by "react-router" plugin. This option is deprecated, please use `oxc` instead. (x3)

vite-config.ts

import { reactRouter } from "@react-router/dev/vite";
import tailwindcss from "@tailwindcss/vite";
import { defineConfig } from "vite";
import devtoolsJson from "vite-plugin-devtools-json";

export default defineConfig({
  resolve: {
    tsconfigPaths: true,
  },
  plugins: [tailwindcss(), reactRouter(), devtoolsJson()],
});

[aniruddhaadak80]

Hi @ReaJason!

Thanks for opening this up! Usually, with these kinds of underlying issues, the first step is double-checking if there is a minor version mismatch in your installed environment tooling vs the actual framework requirements.

Have you tried outright clearing the respective local build/cache directories, forcing a clean slate reinstall, and ruling out any implicit breaking changes from recent patches?

If you are still hitting the exact same bottleneck, dropping a minimal reproduction steps (or specifically the raw error logs) here usually gets it sorted out way faster by the maintainers.

Hope this helps point you in the right direction. Let me know if you make any progress!

[chinfeng]

Hi @ReaJason!

Thanks for opening this up! Usually, with these kinds of underlying issues, the first step is double-checking if there is a minor version mismatch in your installed environment tooling vs the actual framework requirements.

Have you tried outright clearing the respective local build/cache directories, forcing a clean slate reinstall, and ruling out any implicit breaking changes from recent patches?

If you are still hitting the exact same bottleneck, dropping a minimal reproduction steps (or specifically the raw error logs) here usually gets it sorted out way faster by the maintainers.

Hope this helps point you in the right direction. Let me know if you make any progress!

Same with vite@8.0.0 and react-router@7.13.1

[rossipedia]

This is being looked at. To be clear, though, this is just a warning, and most of the esbuild settings are automatically converted to the oxc equivalent.

In my own tests, vite@8 works with react-router@7 as expected, even with the emitted warning.