New updates in payload cms 3.0 from 2.0

Payload CMS 3.0 introduces several updates and changes compared to version 2.0, with a focus on modernizing architecture, improving integrations, and enhancing developer experience:

1. Next.js Integration: The admin panel and API now utilize Next.js instead of Express. This change improves scalability and compatibility, aligning with modern web development practices. Custom routes and middleware can be migrated to Next.js route handlers or hooks​
2. Payload
3. ​GitHub
4. .
5. Updated Configuration:

• next.config.js needs to be updated to use ESM format and wrapped with withPayload for compatibility.
• TypeScript configurations require adjustments, such as using the moduleResolution: bundler option for Next.js compatibility​GitHub
• .

1. Admin Panel Enhancements:

• Deprecated properties like favicon and meta.ogImage are replaced with more flexible options (icons and openGraph.images).
• Admin styles and customizations are moved to Next.js’ modern tooling, such as .scss files under specific folders​GitHub
• .

1. Email System Overhaul: Email functionality is abstracted into adapters, such as nodemailerAdapter, for more flexible email service integration​
2. GitHub
4. .
5. Breaking Changes in APIs: Updates to livePreview, email, and other methods simplify configurations but require migration adjustments. Features like custom CSS for the admin panel now use Next.js layouts instead of inline properties​
6. GitHub
8. .
9. Backward Compatibility: While some Express functionalities can still be used by configuring a custom server in Next.js, this is optional and primarily for legacy codebases​
10. GitHub
12. .