Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tidy up /pages directory #74

Open
fnwbr opened this issue Oct 5, 2023 · 0 comments
Open

Tidy up /pages directory #74

fnwbr opened this issue Oct 5, 2023 · 0 comments

Comments

@fnwbr
Copy link
Member

fnwbr commented Oct 5, 2023

As of Next.js 13 they have also changed the recommended way of structuring an app directory structure: https://nextjs.org/blog/next-13#new-app-directory-beta - and in the following minor releases they have further adjusted it: https://nextjs.org/blog/next-13-1#improved-reliability-and-support-for-app-directory (via)

We should probably follow that restructuring...

Also, when running next build with our current setup, it's falsely assuming that some of our files are pages. When they're just components we're wanting to use inside of other pages. For example /etherpad/actions/AddExistingPad is a component we use inside of /etherpad/[[...roomId]].
image

The solution for the latter problem is to probably make use of this: https://nextjs.org/docs/pages/api-reference/next-config-js/pageExtensions#including-non-page-files-in-the-pages-directory (via)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant