
React.run
Vite
React
Next.js
Node.js
Tailwind CSS
Webpack
Redux.js
PostGraphQL
graphql-yoga
React Admin
Directus
Parse
Observable
node-http-proxy
Nhost
PostGraphQLIt is recommended for developers of all levels who are working with or interested in React. Beginners can benefit from the structured tutorials and foundational information, while experienced developers can find advanced topics and the latest developments in the React ecosystem.
Based on our record, React.run seems to be a lot more popular than PostGraphQL. While we know about 194 links to React.run, we've tracked only 10 mentions of PostGraphQL. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Itโs already been captured. Check out the docs for creating a new React app on react.dev: https://react.dev/learn/creating-a-react-app It throws you straight at Next.js. - Source: Hacker News / 11 months ago
> The train of thought is โwhat is everyone using? Iโll use that tooโ I'm not so sure about that. We're seeing Next.js being pushed as the successor of create-react-app even in react.dev[1], which as a premise is kind of stupid. There is something definitely wrong going on. [1] https://react.dev/learn/creating-a-react-app. - Source: Hacker News / 11 months ago
The React documentation is infamously responsible of recommending Next as a "default". After a lot of backlash it got somewhat toned down, but it's still the first thing they suggest[1] for creating a new app [1] https://react.dev/learn/creating-a-react-app. - Source: Hacker News / 11 months ago
In times when the official React documentation says:. - Source: dev.to / 12 months ago
Vercel's playbook with Next so far has been to make convoluted features that exist solely to pad out how much people spend on hosting costs. They also make sure that hosting it anywhere but Vercel comes with footguns, even though theoretically you can host your Next app anywhere you want (and it's gotten better recently solely because of backlash). See https://opennext.js.org/ for example. They've been so... - Source: Hacker News / about 1 year ago
If you point is to abstract all the CRUD/GraphQL application, Go isnโt needed. You can go with PostgREST or Postgraphile. Source: over 3 years ago
What do you mean locally? Hasura is OSS, and you can run it locally (you have autogenerated SQL statements) Here you can just use Nhost and its CLI; Alternatives are https://github.com/graphile/postgraphile or dgraph as you mentioned. Hasura is working on support for sqlite, so you may have some blockers there, you can also look into the Prisma engine which has GQL as an intermediate (for resolvers, for example). - Source: Hacker News / over 3 years ago
I've personally found Postgraphile to be fantastic. Nicer to use than Hasura and fully OSS: https://github.com/graphile/postgraphile/. - Source: Hacker News / about 4 years ago
Hi all, this sounds very cool. How does pg_graphql compare to Postgraphile? https://github.com/graphile/postgraphile (besides I guess running in the DB with PLpgSQL instead of as a NodeJS server) Did you think about integrating Postgraphile with the Supabase ecosystem or have specific limitations with it? Thanks! - Source: Hacker News / over 4 years ago
If youโre open to learning Postgres, Iโd recommend postgraphile (https://github.com/graphile/postgraphile). Been using it for the past 2.5 years and only have good things to say. Source: over 4 years ago
Vite - Next Generation Frontend Tooling
graphql-yoga - ๐ง Fully-featured GraphQL Server with focus on easy setup, performance & great developer experience - prisma-labs/graphql-yoga
React - A JavaScript library for building user interfaces
React Admin - A frontend Framework for building B2B applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Material Design
Next.js - A small framework for server-rendered universal JavaScript apps
Directus - Free and Open-Source Headless CMS