2024 Roadmap: We’ve Made a Next.js Decision (And A Lot More)
Вставка
- Опубліковано 17 вер 2024
- What's to come for Payload in 2024? James Mikrut breaks it all down, including a decision around the much anticipated move to Next.js.
Love what we're up to? Give us a star: github.com/pay...
Questions? Take it to Discord: / discord
I am ready to go all in on nextjs + payload. I am looking forward to 3.0!
Tried Directus?
@@morespinach9832i have! It is great. I work with react so payload being react based is what I prefer to directus being Vue based
I am new here and i am glad this video is 2 months old so i dont wait that long ❤
Very excited to hear about the upcoming WebSockets feature. That is going to be a huge leap forward for Payload.
Agreed! I need it!
Excited about the move to Nextjs from express. Currently making an app with 2.0 and plan to migrate 2 of my websites to payload soon. One from Strapi, and one from a custom cms.
What did you dislike about Strapi?
@@morespinach9832 no Typescript, janky way of using dynamic inputs, customizing with code not as straight forward.
James, congratulations on the Next.j move and excited about Localization features!
Thanks @rbarona - both nextjs and the localization stuff are going to be huge. Can't wait!
I will be cooking with the 3.0 beta from the second it drops 🙌🏻 Godspeed, team!
I know you will! I can't wait to hear your feedback!
Sqlite support could open a lot of use cases now that services like turso are killing it! Glad to hear its a priority!
I really love the idea of payload. I'm currently in no need of it and as such not in a rush to try it out. However, once the transition to next js and version 3, I guess, is out I'll definitely try it out and possibly give myself an excuse to use it.
This is all very exciting. Upvoted multiple localizations and nextjs support. Been using next-payload and improvements to cold starts and HMR would be game changers. I also had to setup multiple locale fields manually with a group .en and .fr fields since the current locale system was confusing to my editors so doing this automatically would be awesome. Looking forward to the many improvements!
Thanks for the kind words! I am pumped as well. So excited for all this stuff to come out.
Congratz guys - really looking forward to the Nextjs integration - I am also convinced it's gonna be a game changer - product & business-wise!
the triangle company strikes again ,joking aside really excited with all you and the team are doing
I'm in love with this product! Thanks Payload team.
Yes, right move :D WP of Node.js is becoming true.
I am very excited for this!
Awesome work guys ❤, Nextjs ❤ Payload @❤
Guys, can you make sure that Payload can be still used with express ? Also nextjs is well known for hosting out of vercel -> being difficult inherently (open next). Also what about people who don't use Next& React?
10000%. Payload will absolutely still work with Express - we need that ourselves. Definitely not going to lose sight of that. And for those that don't want to use React or Next on their frontend, they'll still be able to combine any other frontend framework in the same Express server as Payload, just as they do now. Nothing will change there!
@@JamesMikrut so what /where is it using next.js?
Sounds like you are building an operating system for the web.
I would love for the website docs to be updated around some of what i see as somewhat common issues. Generating types, switching to versioning and localization and the changes that makes behind the scenes, and maybe a few more hook examples....I have had to dig to find these solutions, and the search on the site is ok but it is limiting in that it returns so few results
You got it. Thanks for the feedback!!!
Yea, ill be ready to go when the move away from express happens.
what about a WP gutenberg style editor?
it would make payload cms outstanding
I want to, but I dont care!! I love your ethos and vision just knock it out of the park.
When we can expect 3.0 beta?
Did you consider moving to Remix instead of NextJs? Remix now has a Vite plugin and offers a lot more flexibility than NextJs. It will be harder to make self host deployments to other providers instead of Vercel
Yes, lots, but the significant majority of our current users are building on Next.js over Remix and the main reason that we're looking at Next.js in specific is because we need React Server Components, specifically. The biggest driving factor for us here is to clearly and logically define the boundary between server and client, and that is precisely what RSCs are for. Also, I have been self-hosting Next.js apps for about 6 years and have never had a problem. How is it harder to self-host Next.js vs. Remix?
@@JamesMikrut vercel has such a closed hosting system that a bunch of people started: Open Next ( just to help demystify ). Is there any chance to not jump on the Nextjs train yet?
@@klausss yes, there's a chance that this will not work out how we expect it to, of course. If our work over the next few months doesn't dramatically improve the DX of where we're at now, and the benefits end up marginal, then we'll stick with Express or look at other alternatives. But honestly from our PoC so far it is looking promising. We will try and be transparent throughout the process!
Hello. I am currently trying to build an e-commerce store with payload. Pls can you help me with how to integrate other payment gateways as Stripe is not allowed in my country, Nigeria?
Has anyone told you that you look like chris pine?
Ha, yes, once or twice 😊 I don't see it personally but I'll take it!
So in 4 months they went from 72 issues to 215 😂, many with no response for weeks! I tried it and encountered numerous bugs as well. Not a good look sneek.
let priorityOne: number[] = [1 ... 100]