Pothos Alternatives

pothos reviews and mentions

• When Do You Use Global Types in Your Project?
  1 project | /r/typescript | 26 Mar 2023

  A project I maintain Pothos uses a global namespace with a bunch of interfaces to allow plugins to extend interfaces defined in core or other plugins. This allows plugins to add new options and methods to objects and classes without the other packages needing to know anything about them.

• Full-Stack GraphQL-APIs in TypeScript without codegen
  1 project | /r/nextjs | 16 Mar 2023

  I noticed this being shared around on Twitter the other day - pretty handy, as I'm currently trying to architect a similar experience for my job using Pathos and graphql-codegen.

• Ask HN: What would be your stack if you are building an MVP today?
  47 projects | news.ycombinator.com | 26 Jan 2023

  - tRPC

  But I'd likely throw out Clerk a cheaper option:

  - Supertokens, and also since Supertokens is easy (lots of enthusiastic reports about it), has a managed solution (which is cheaper than the alternatives), is secure and scalable (rotating refresh tokens with JWTs), open source, has magic links, and the architecture of Supertokens would allow me to simply and quickly eject to self-hosting it if/when I'd eventually need to (if the app ever reaches mass-market scale).

  And I might throw out tRPC for the equivalent GraphQL experience (esp. if business strategy dictates I need a 3rd party API):

  - GQty.dev on the client, for inferred queries/mutations. For rapid dev speed. Simple code example: https://gqty.dev/docs/intro Then move to URQL or Relay at scale, or just skip GQty and go with URQL from the start (if scalability trumps dev speed).

  - Pothos http://pothos-graphql.dev on the server, for auto building the schema from your TS code (aka. code-first). Better than Nexus (e.g. Max Stoiber moved from Nexus to Pothos on his Bedrock starter template because Pothos is best in class: https://bedrock.mxstbr.com/tools/pothos/ ).

  And I might throw out NextJS (Webpack) for the equivalent experience in Vite:

  - vite-plugin-ssr, since both architectural control (libraries > frameworks) and Vite rocks. I'd likely then have to make solito-vite https://github.com/nandorojo/solito/discussions/157 to have a unified navigation between React Native and Web, but Solito is allegely tiny, so recreating it should be doable.

  (If doing all of these replacements, maybe starting from scratch would be easier than modifying create-universal-app ... That said, I think if someone made a starter repo with the above choices it would be a real killer!)

  Then I'd also likely use:

  - Vercel (and try their Edge Functions, for a serverless sweet v8 isolates experience without slow cold starts), or maybe Cloudflare Workers (cheaper, slightly more hassle?) for hosting.

  - Planetscale or Supabase for the DB. (Not brave enough to try EdgeDB or SurrealDB just yet, though EdgeDB is close..) Unless I had a specific use case where a more specialized/optimized DB would make sense.

  This stack should stick even post-MVP, as it's not only optimized for a solo developer but for scalability.

• Real World Rust Backend For Web APIs (GraphQL / REST)
  8 projects | /r/rust | 24 Dec 2022

  Have you used Pothos? It's a way to make GraphQL schemas in TypeScript, in a type-safe way. So the creator of Prisma Client Rust is thinking about making a Pothos-style API based on the t builder pattern:

• What to use with Apollo Server v4 to achieve type-safety?
  3 projects | /r/graphql | 19 Dec 2022

  I would recommend Pothos (https://pothos-graphql.dev/) as a more modern alternative to typegraphql or nexus.

• Apollo Layoffs
  6 projects | news.ycombinator.com | 15 Dec 2022

  Depends on language, I've build GraphQL servers in a few, though mostly JavaScript and Python. For Python I used to use Graphene, these days I use Strawberry.

  For JavaScript, I originally used graphql-js and express-graphql, as these were the original libraries and I was a literal day 1 adopter. All the libraries are essentially just wrappers around graphql-js, so it's still viable to use directly. But for schema-building I now use Pothos (https://pothos-graphql.dev/), I'd probably use graphql-helix as the http layer (https://github.com/contra/graphql-helix).

• Achieving end-to-end type safety in a modern JS GraphQL stack
  9 projects | dev.to | 24 Nov 2022

  Pothos is a breeze of fresh air when it comes to building GraphQL APIs. It is a library that lets you write code-first GraphQL APIs with an emphasis on pluggability and type safety. And it has an awesome Prisma integration! (I am genuinely excited about this one, it makes my life so much easier.)

• Pothos – Convert TypeScript to GraphQL Schema
  1 project | news.ycombinator.com | 27 Sep 2022
• How to Build a Type-safe GraphQL API using Pothos and Kysely
  5 projects | dev.to | 29 Aug 2022

  In today's article we are going to create a GraphQL api using the Koa framework together with the GraphQL Yoga library and Pothos. In addition, we will use Kysely, which is a query builder entirely written in TypeScript.

• Extreme Explorations of TypeScript's Type System
  15 projects | news.ycombinator.com | 27 Jun 2022

  If you're a GraphQL developer, Pothos is the best example - all your user-defined types just fits in it like a glove 99% of the time. It definitely makes the most use of TS generics.

  https://pothos-graphql.dev/

  (I'm a bit sleepy, so this is the main one I can think of at the moment that I really enjoy using.)

• A note from our sponsor - InfluxDB
  www.influxdata.com | 26 Apr 2024

  Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →