Just wanted to see what people think nextjs using non-standard characters in file names

[patrick99e99]

To me, this was one of the dumbest decisions ever made, and has caused me so many moments of frustration and annoyance when trying to interact with files in the terminal. I had to modify my terminal's word boundary rules so that double clicking could select an entire path, but that introduces negative consequences at other times when working with other projects...

[aniruddhaadak80]

Hello @patrick99e99,

When working with Next.js, especially with file-system routing and deployment strategies, a lot of quirks usually come down to how the build output is handled (App Router vs Pages router).

Make sure your next.config.js matches your deployment target (like using output: "standalone" if you are deploying on Docker/Node instead of Vercel). Feel free to share more of your config if the issue persists! Let me know if you need more dedicated debugging here.

Hope this points you in the right direction! Let me know how it goes. Happy coding!

[patrick99e99]

Umm.. no it does not point me to the right direction.

My complaint is nextjs USING (, [, ), ] characters in file names because that makes interacting with those files in the terminal a nightmare.