How to configure react-router to use the production build?

[david-szabo97]

Since remix-run/react-router#12437 it's impossible to do a production build which uses react-router/dist/production. The PR is 6 months old and it doesn't state any alternative on how to do a production build.

Since every react-router build is a development build, we are bombarded with No route matches URL errors in our logs. And I also wonder if there is any performance hit caused by using a development build.

$ npm run build && npm run start

> start
> react-router-serve ./build/server/index.js

[react-router-serve] http://localhost:3000
Error: No route matches URL "/asd"
    at getInternalRouterError (my-react-router-app/node_modules/react-router/dist/development/chunk-DQRVZFIR.mjs:4514:5)
    at Object.query (my-react-router-app/node_modules/react-router/dist/development/chunk-DQRVZFIR.mjs:2728:19)
    at handleDocumentRequest (my-react-router-app/node_modules/react-router/dist/development/chunk-DQRVZFIR.mjs:11031:40)
    at requestHandler (my-react-router-app/node_modules/react-router/dist/development/chunk-DQRVZFIR.mjs:10946:24)
    at my-react-router-app/node_modules/@react-router/express/dist/index.mjs:28:28
No routes matched location "/asd" 
GET /asd 404 - - 27.355 ms

[punkpeye]

Pretty sure there is indeed a performance hit:

https://discord.com/channels/770287896669978684/770287896669978687/threads/1438582197513748660

I am troubleshooting it in this thread.

The closest workaround I have found so far is to override at the resolver level:

remix-run/react-router#14102 (comment)