pothos
Avo
pothos | Avo | |
---|---|---|
24 | 48 | |
2,244 | 1,379 | |
- | 2.4% | |
9.2 | 9.7 | |
5 days ago | 5 days ago | |
TypeScript | Ruby | |
ISC License | Creative Commons Attribution Non Commercial 2.5 Generic |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pothos
-
When Do You Use Global Types in Your Project?
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
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?
- 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)
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?
I would recommend Pothos (https://pothos-graphql.dev/) as a more modern alternative to typegraphql or nexus.
-
Apollo Layoffs
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
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
-
How to Build a Type-safe GraphQL API using Pothos and Kysely
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
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.)
Avo
-
Show HN: Build your startup or side project faster with these SaaS templates
Quality is often much better with these kinds of templates and frameworks, because the creators often can make better default choices.
For example, Avo (https://avohq.io) and Bullet Train (https://bullettrain.co/) are IMHO both much higher quality out of the box than what a typical intermediate Rails developer could accomplish in months of full time learning and coding.
-
Mastering Rails Web Navigation with link_to and button_to Helpers - Part 2
<%= link_to(@car) do %> <%= @car.name %> -- Check this car! <% end %> cars/1"> Tesla -- Check this car! <%= link_to "https://avohq.io/" do %> AvoHQ - The Best Rails Guide <% end %> https://avohq.io/"> AvoHQ - The Best Rails Guide
-
Ready System with a Modern Stack and Many Features Using Ruby 3.2, Rails 7.0 and Avo 2
Access the Avo, and click on Sign Up. After completing registration, click on your profile icon and select Subscriptions, then Choose a plan, choose the Pro version and click on Start 30 day trial. The system URL is not required, click Subscribe. Now you will have your key to use the Avo 2 Pro version for 30 days.
- The Open Source Ruby on Rails SaaS Framework
- What are the cons of using something like https://avohq.io/ ?
-
Experience using Retool and Ruby on Rails
But there's another alternative for Ruby on Rails. This is a shameless plug, but why don't you try Avo?
-
Roast my page: Avo - A low-code tool that helps developers create internal tools, admin panels, and CMS-es with Ruby on Rails
URL: https://avohq.io
-
Ask HN: What would be your stack if you are building an MVP today?
Nothing really beats Rails. Use something like Jumpstart (jumpstartrails.com) and Avo (https://avohq.io) and you scaffold a full consumer-ready app in literally a few hours.
The thing that bugs me the most with Next.JS and the whole JAMStack movement is that, yeah, you get from "git clone" to deployed on Vercel in two minutes, but if you need to create real app features like a sturdy admin, accounts, authorization, proper asset management, CI/CD, it takes a whole lotta time. I'm not even touching the most common app features.
-
Show HN: Refine v3.97 – Open-source React framework for building CRUD apps
Hey. I'm Adrian, author of Avo. Avo is similar to Refine but for Ruby on Rails.
It helps developers create CRUD-like applications such as internal tools, admin panels, Content Management Systems and user-facing apps.
I love seeing more and more movement in this space.
https://avohq.io
-
Write admin tools from day one
Laravel has Nova, Django has Django Admin, and now, Rails has Avo.
https://avohq.io
*I am the author of Avo
What are some alternatives?
nexus - Code-First, Type-Safe, GraphQL Schema Construction
ActiveAdmin - The administration framework for Ruby on Rails applications.
graphql-upload - Middleware and an Upload scalar to add support for GraphQL multipart requests (file uploads via queries and mutations) to various Node.js GraphQL servers.
motor-admin-rails - Low-code Admin panel and Business intelligence Rails engine. No DSL - configurable from the UI. Rails Admin, Active Admin, Blazer modern alternative.
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
RailsAdmin - RailsAdmin is a Rails engine that provides an easy-to-use interface for managing your data
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.
Administrate - A Rails engine that helps you put together a super-flexible admin dashboard.
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
Wallaby - Autocomplete the resourceful actions and views for ORMs for admin interface and other purposes.
gqtx - Code-first Typescript GraphQL Server without codegen or metaprogramming
Upmin Admin - Framework for creating powerful admin backends with minimal effort in Ruby on Rails.