Allow mjs extension for route config file

[sdavids]

I'm using React Router as a...

framework

Reproduction

https://stackblitz.com/edit/github-gdzzgosz

react-router/packages/react-router-dev/config/config.ts

Line 740 in 228b17e

const entryExts = [".js", ".jsx", ".ts", ".tsx"];

System Info

System:
    OS: macOS 12.7.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
    Memory: 569.35 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 22.13.1 - ~/.local/run/fnm_multishells/1019_1737974614999/bin/node
    npm: 10.9.2 - ~/.local/run/fnm_multishells/1019_1737974614999/bin/npm
  Browsers:
    Brave Browser: 131.1.73.104
    Chrome: 131.0.6778.267
    Safari: 17.6
  npmPackages:
    @react-router/dev: 7.1.3 => 7.1.3 
    @react-router/node: 7.1.3 => 7.1.3 
    @react-router/serve: 7.1.3 => 7.1.3 
    react-router: 7.1.3 => 7.1.3 
    vite: 6.0.11 => 6.0.11

Used Package Manager

npm

Expected Behavior

app/routes.mjs is allowed.

Actual Behavior

$ ls app/routes.*
app/routes.mjs
$ node --run dev
Error: Route config file not found at "app/routes.ts".
    at createConfigLoader (/tmp/test/node_modules/@react-router/dev/dist/vite.js:486:11)
    at createContext2 (/tmp/test/node_modules/@react-router/dev/dist/vite.js:775:24)
    at watch (/tmp/test/node_modules/@react-router/dev/dist/vite.js:750:15)

[github-actions]

To align with our new Open Governance model, we are now requiring that all issues have a minimal and runnable reproduction. To that end, we're doing some housekeeping in the repo to clean up existing issues that do not have a valid reproduction. This should get us down to a more manageable number of issues and allow us to be more responsive to existing and newly filed issues.

We're using a GitHub actions script to identify issues without a reproduction by looking for a StackBlitz, CodeSandbox, or GitHub link in the issue body. This won't be perfect, so if this issue has a reproduction on another platform, please comment back on here, and we can re-open the issue. Similarly, if there's a reproduction buried in a comment, please move the link into the description and comment back. Please tag @brophdawg11 or @brookslybrand in your comment so we get a notification as well 🙂.

If this issue did not have a reproduction but is still valid, or if you wish to start with a fresh issue, please create a new issue with a fresh reproduction against v7 and link to this issue in the new description.

If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support, it can be considered for implementation.

If you have any questions, you can always reach out on Discord. Thanks again for providing feedback and helping us make React Router even better!

[sdavids]

Why is this getting closed?

This is the third issue I participate in where your bot closes an issue without any way for a human to react — and for a human reading it, it is clear what to do/what the issue is …

@brophdawg11 @ryanflorence Do you want humans participating in your project?

Yes, there is the issue of AI creating slop issues …

But the way this bot is behaving — and you giving it its power: It is just a matter of time before humans abandon your project.

It is just a waste of my (our) time and disrespectful to be treated in this way.

[sdavids]

You already have this overly restrictive issue template and it is still not enough …

[sdavids]

If this issue did not have a reproduction but is still valid, or if you wish to start with a fresh issue, please create a new issue with a fresh reproduction against v7 and link to this issue in the new description.

This is just a slap in the face for every human.

• rant on *

Someone takes the time to adhere to your restrictive issue template

… spends 10-20 minutes creating a humanly-understandable issue …

… gets rejected by an asinine bot … apparently incapable of interpreting the issue template and issue at hand.

You can now waste another 10-20 minutes … hope for your bot not to reject you again

… a human then says: f no!

I will spend my time with another community.

• rant off *

Please reconsider your usage of the bot, thanks.

The best part is: A human already looked at this issue, understood it, and categorized it.

But nope, the bot does not care … let’s waste the time of humans.

[brophdawg11]

It is just a waste of my (our) time and disrespectful to be treated in this way.

I mean, one could argue you're being pretty disrespectful yourself, so let's tone it down and we're happy to work with you to get the issue resolved.

We request runnable reproductions specifically because it's not "AI Slop" issues that are the problem. It's human-created issues that provide a few lines of code and lack a ton of additional context to make the issue actionable. If it's wasted human time you're concerned with - the real issue is the time maintainers need to spend trying to manually reconstruct the actual issue from issues that don't provide enough context. Anthony Fu has a nice article discussing why reproductions are required.

The comment specifically states "This won't be perfect" because we get way too many issues to look at every one in detail mentally reconstruct code samples in our heads to see if it's actually actionable. So yes, we've added a bot that does a pretty good job of identifying issues without a reproduction. We also specifically said that we can re-open issues where appropriate - so a simple, polite, response from you would have been enough 🙃 .

You can now waste another 10-20 minutes

Did you consider actually trying to use the links we provide before firing off your comments above? It took <60 seconds seconds for me to open https://reactrouter.new and change then file extension and produce a perfectly acceptable reproduction: https://stackblitz.com/edit/github-gdzzgosz. Next time, please consider if it would really be that much effort to create a reproduction instead of ranting at us in comments.

[brophdawg11]

As stated, it was not a runnable reproduction