App Directory, is it possible to define routes without using page.js/tsx files? If so, what is the recommended alternative for creating pages or routing logic?

[gsmental]

"We've been using the pages directory for years, but now we're looking to implement server-side rendering features. However, one issue we've encountered with the new App Directory structure is that the page.tsx/page.js files are repeated in every directory, which makes the setup more complicated. Sometimes, we accidentally replace a page in the wrong directory, causing us to lose newly developed pages. This has become a significant problem for our workflow."

[icyJoseph]

AFAIK, no, the file system routing, using page.tsx and others, is the way to go. You can use custom page extensions, https://nextjs.org/docs/app/api-reference/config/next-config-js/pageExtensions, which can help to have a richer, more meaningful name.

Sometimes, we accidentally replace a page in the wrong directory, causing us to lose newly developed pages. This has become a significant problem for our workflow."

How does that even happen?