Install Payload Into Any Next.js App With One Line — 3.0 Beta Is Here!

🎉🎉 Big news: 🚀🚀 Payload 3.0 Beta is now available, making Payload truly Next.js native! You can get started in one line: npx create-payload-app@beta

Chapters:
0:00 3.0 Is Here
0:50 A Turning Point for Headless CMS Industry
1:39 Combining Payload Into Any Next.js App
4:58 Modular Local API: Use Payload Anywhere
7:27 Server-side HMR
8:32 Deploy to Vercel
9:35 Bundling: Get Turbopack Out of Box
12:03 Migration: Use Express If You Want To
13:03 Migration and Imports: Payload Has Moved to ESM
13:46 React Components As Client or Server Components
16:30 What's Next: Beta to Stable
17:03 What's Next: Docs
17:34 What's Next: Stable Release

Love what we're up to? Give us a ⭐
https://github.com/payloadcms/payload

Payload 3.0 Demo on Github:
https://github.com/payloadcms/payload...

The big takeaways::
— Turbopack works out of the box (this will get faster over time)
— The Payload admin UI is built with React Server Components and automatically eliminates server-side code from your admin bundle, completely alleviating the need to use Webpack aliases to remove hooks, access control, etc.
— Payload is now fully-ESM across the board
— GraphQL is now initialized only when you hit the GraphQL endpoint, and does not affect overhead of REST API routes
— All UI components have been abstracted into a separate @payloadcms/ui package, which will be fully documented and exposed for your re-use once we hit stable 3.0 or before
— You can run your own Next.js site alongside of Payload in the same app
— You can now deploy Payload to Vercel, and there will be official support for — Vercel Blob Storage coming soon (so no S3 needed for files)
— Server-side HMR works out of the box, with no need for nodemon or similar. When the Payload config changes, your app will automatically re-initialize Payload seamlessly in the background
— All custom React components can be server components by default, and you can decide if you want them to be server components or client components
— Sharp has been abstracted to be an optional dependency
— Payload now relies on the Web Request / Response APIs rather than the Node Request / Response
— Express can still be used with Next.js' Custom Server functionality
— Payload itself has slimmed down significantly and can now be fully portable, run anywhere. You can leverage the Payload Local API completely outside of Next.js if you want.
— The data layer, including the shape of the database Payload used and the API responses in 2.0, has not been affected whatsoever

With a lot more to come.

payloadcms.com
github.com/payloadcms/payload
discord.gg/payload