Replies: 2 comments
-
Just ran into this as well, migrating an app from Vite to Next. The existing router uses the pages directory, and I spent about a day debugging why it wouldn't build! Since we aren't using Next pages router, it would nice to disable it. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I've just renamed Btw we need a proper solution, as there is app folder for routing purposes, it would be great to disable pages router and special rules for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
We're beginning to upgrade to Nextjs 15 RC to see what we need to update (we are on v14@latest). One of the things we'd like to use in our
src
folder is a folder calledpages
. We have our routes listed using the app router (folder/files) and that works great. And from a code organizing POV we'd like to create a folder calledpages
and add components there as well. (without of course having those components (folder/files) in any way automatically used for routing).Currently, if we add the
pages
folder and add anindex.tsx
or aMyComponent/index.tsx
, they are also treaded as a route and will be rendered as a page in the browser.We also attempted to use
pageExtensions: ['page.tsx', 'page.ts', 'page.jsx', 'page.js']
in the config file but then we'll have to update ALL our files in the app router directory as well.Is there a way to just disable the
pages
functionality and have it be a 'dumb' folder?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions