Can not find module '@payloadcms/next/views' or its corresponding type declarations.

[shawqicauses]

Describe the Bug

I tried create-payload-app@beta and it fails in installing dependencies. So, I tried to install Payload and its dependencies my self. But, @payloadcms/next/views does not have view module.

Link to the code that reproduces this issue

https://github.com/payloadcms/payload-3.0-demo/blob/main/src/app/(payload)/admin/%5B%5B...segments%5D%5D/page.tsx

Reproduction Steps

1. run npx create-payload-app@beta
2. run npm install --save payload@beta @payloadcms/next@beta @payloadcms/richtext-lexical@beta @payloadcms/payload-cloud@beta @payloadcms/db-mongodb@beta graphql@^16.8.1 --legacy-peer-deps

Which area(s) are affected? (Select all that apply)

area: core

Environment Info

Payload v3.0 and Next.JS v15

[PatrikKozak]

Hey @shawqicauses - we are officially out of beta and have released payload 3.0!

So when creating a new project, you just need to do npx create-payload-app - no need to append @beta to it anymore.

It'll be on 3.0 out of the box.

Can you try this out and let me know if you're still experiencing issues with your dependencies being installed? Thanks!

I just tested it out and didn't experience any issues - going to close this but if you are still seeing issues, I'll reopen!

[akhrarovsaid]

Hey @shawqicauses,

Sorry to hear about the troubles you're experiencing! I see a few issues in the project where you're trying to install Payload into and I'd like to list some things that come to mind that could help.

1. Payload v3 require both Next v15+ and React 19 (where react and react-dom are pinned to these versions)
2. As Patrik mentioned, installing Payload v3 going forward does not need the @beta tag, since you use npm this should work for you: npx create-payload-app (maybe try with the --legacy-peer-deps flag?)
3. With the current way your app is scaffolded out, when you install Payload, you will receive invalid html structure errors due to having a top-level root layout that will conflict with Payloads. See the website template to see how you can avoid this.

It may be worth it to test out Payload in a new project using something like the website template as a guide, and then move over the necessary things from your current project since it's a starter anyway. In this way you can get more comfortable with Payload and have a working app.

[PatrikKozak]

@akhrarovsaid Thanks for the additional info here!

@shawqicauses Did you happen to give the above a try?

[shawqicauses]

@PatrikKozak Yes, you can close this issue.

In my legacy starter template because of React.JS version and other libraries like ShadCN/UI, Payload CMS could not download its packages correctly, I created a new Next.JS application and initialised Payload and it worked just fine. I created another issue for something else did not work as intended but it is closed now. In general, everything is okay now, thanks!

[github-actions]

This issue has been automatically locked.
Please open a new issue if this issue persists with any additional detail.