5 ms·
The JS ecosystem seems a lot more hesitant to bundle features into frameworks à la Rails/Laravel & friends, but Redwood.js sounds like what you're looking for.
by chazhaz 4y ago
The JS ecosystem seems a lot more hesitant to bundle features into frameworks à la Rails/Laravel & friends, but Redwood.js sounds like what you're looking for. The ORM it uses is Prisma, which works really well on its own too.
https://redwoodjs.com https://redwoodjs.com
https://www.prisma.io https://www.prisma.io
- nikolasburk 4y agoIf you want to learn about Redwood, I'd also recommend Amy's talk about it from Prisma Day two weeks ago: https://www.youtube.com/watch?v=_zJ44wmo1Ro&ab_channel=Prisma https://www.youtube.com/watch?v=_zJ44wmo1Ro&ab_channel=Prism... :)
- shafyy 4y agoRedwood and Prisma look nice! But what I like more is a focus on serverside rendering and as few build steps as possible, like Fresh. I also find Deno more appealing than Node (simplicity). But yes, I guess if I would need to pick a more mature framework with JS, Redwood would be the way to go.
- lewantmontreal 4y agoPrisma is a nice product but I wouldn’t use it in production yet. It is prone to race conditions as it does not use native upserts, opting instead for Rails-style check-if-exists-insert-if-doesnt.