// the find
redwoodjs/graphql
RedwoodGraphQL
RedwoodJS is a full-stack JavaScript/TypeScript framework that wires together React, GraphQL (via GraphQL Yoga), Prisma, and a file-based router into a single opinionated package. It's aimed at teams who want Rails-style conventions for JS apps without the framework-assembly tax. The repo is currently in transition: the stable 'Arapahoe' epoch uses the classic GraphQL API model, while the in-progress 'Bighorn' epoch is pivoting toward RSC + Server Actions.
- The Prisma + GraphQL SDL + service layer pattern is genuinely well-thought-out — SDL files are the contract, services are the logic, and the generator scaffolding actually produces useful code rather than skeleton noise.
- First-class support for both serverless (Netlify, Vercel) and traditional server deployments from the same codebase is a real differentiator — most frameworks force a choice.
- The testing setup (Jest + Storybook baked in, fixture projects in `__fixtures__/`) reflects serious production experience, not afterthought.
- Active changeset discipline and a large contributor list signal genuine community maintenance, not a solo author's abandoned experiment.
- The framework is mid-pivot: the README promotes the 'Bighorn' RSC epoch as aspirational but explicitly warns it has no production release. If you start a project today on stable Arapahoe, you're adopting a model the team is moving away from.
- All GitHub Actions CI workflows are `.disabled` — the repo's own CI is turned off, which is a yellow flag for contribution confidence and release quality gates.
- GraphQL as the mandatory API layer adds overhead that most CRUD apps don't need; the Bighorn pivot away from it suggests even the maintainers agree, but you're stuck with it on stable.
- The monorepo is large and the dependency graph complex enough that they ship a `.dependency-cruiser.mjs` config just to manage it — onboarding friction is real, and framework bugs can be buried deep in package interdependencies.