autonomic-cooperative/nextload
0
0
Fork 0
Code Issues 11 Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
James Mikrut 2024-03-07 13:11:14 -05:00 committed by GitHub
parent b0656b70b8
commit bfd758ca99
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 25 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
README.md
View File

@ -9,35 +9,37 @@ We're actively working toward a beta release, and then a full stable release as
### Highlights ### Highlights
1. Payload is now Next.js-native 1. Payload is now Next.js-native
2. Turbopack works out of the box (this will get faster over time, expect more here) 1. Turbopack works out of the box (this will get faster over time, expect more here)
3. 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. 1. 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.
4. GraphQL is now initialized only when you hit the GraphQL endpoint, and does not affect overhead of REST API routes 1. Payload is now fully-ESM across the board
5. 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 1. GraphQL is now initialized only when you hit the GraphQL endpoint, and does not affect overhead of REST API routes
6. You can run your own Next.js site alongside of Payload in the same app 1. 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
7. 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) 1. You can run your own Next.js site alongside of Payload in the same app
8. 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 1. 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)
9. 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 1. 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
10. Sharp has been abstracted to be an optional dependency 1. 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
11. Payload now relies on the Web Request / Response APIs rather than the Node Request / Response 1. Sharp has been abstracted to be an optional dependency
12. Express can still be used with Next.js' Custom Server functionality 1. Payload now relies on the Web Request / Response APIs rather than the Node Request / Response
13. 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. 1. Express can still be used with Next.js' Custom Server functionality
14. The data layer, including the shape of the database Payload used and the API responses in 2.0, has not been affected whatsoever 1. 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.
1. The data layer, including the shape of the database Payload used and the API responses in 2.0, has not been affected whatsoever
### Work to come ### Work to come
We are making this available to our community so that we can gather your feedback and test the new approach that Payload is taking. Don't expect it to be fully functional yet. There are some things that we are aware of that are not yet completed, but we're going to keep blazing through the remaining items as fast as we can to reach stable 3.0 as quickly and efficiently as possible. Here are a few of the items that we are still working on (not a full list): We are making this available to our community so that we can gather your feedback and test the new approach that Payload is taking. Don't expect it to be fully functional yet. There are some things that we are aware of that are not yet completed, but we're going to keep blazing through the remaining items as fast as we can to reach stable 3.0 as quickly and efficiently as possible. Here are a few of the items that we are still working on (not a full list):
1. `beforeDuplicate` hooks 1. `beforeDuplicate` hooks
2. The config `preview` function 1. The config `preview` function
3. Focal point / cropping 1. Focal point / cropping
4. Documentation 1. Documentation
5. Vercel Blob Storage adapter 1. Vercel Blob Storage adapter
6. Lots of bugs for sure 1. Lots of bugs for sure
7. 100% of tests passing 1. 100% of tests passing
8. Overall speed improvements 1. Compiler speed improvements
9. Support for all official plugins 1. Overall speed improvements
10. An install script to be able to install Payload easily into any existing Next.js app 1. Support for all official plugins
11. A full list of breaking changes for 2.0 -> 3.0, including an in-depth migration guide 1. An install script to be able to install Payload easily into any existing Next.js app
1. A full list of breaking changes for 2.0 -> 3.0, including an in-depth migration guide
### Technical details ### Technical details