phero
garph
phero | garph | |
---|---|---|
21 | 27 | |
311 | 1,287 | |
0.3% | 1.0% | |
6.5 | 7.4 | |
3 months ago | 2 months ago | |
TypeScript | TypeScript | |
Apache License 2.0 | MIT License |
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.
phero
-
Node.js 20 is now available
That's one of the reasons that drove me to create Phero: https://phero.dev
-
Full-Stack TypeScript with tRPC and React
Iโm one of the authors of Phero. Itโs goal is similar to tRPC: fullstack typesafety between servers and clients.
One difference is syntax: Phero leverages the TS compiler api to generate parsers for your backend functions. It will parse input and output or your api, automatically, based on the types you define for your functions. It will generate a declaration file of your api and generate an RPC style client SDK for your frontend. Another difference is that it aims to be more batteries includes.
[1] https://github.com/phero-hq/phero
Comparison: https://phero.dev/docs/comparisons/tRPC
- Framework for REST API that builds a complete-ish API given a model?
-
Using API routes for large projects
Shameless plug: you could also use https://phero.dev
-
No errors when fetched data is a 'string' even though interface property type should be a number.
Long story short: when fetching data, you should be validating the data, before casting it to a type youโre expecting it to be. There are a lot of different approaches for this, but being the go-author my favorite would be Phero (https://phero.dev). With this, you can build your API in typescript as well, automatically generate a client for your frontend to call the API. Phero will make sure all data is correct in runtime, automatically.
-
Best schema validator for intellisense performance?
For those looking for an alternative: Definitely check out https://phero.dev. As the co-creator Iโm totally biased of course, but thanks to its build-step IDE-performance is great ๐๐
-
I've made a big comparison table of nodejs RPC frameworks. Hope you like it ;)
What about Phero? https://phero.dev
- How you make typesafe front/backend API
-
KitaJs Survey - No runtime code, fast as bare metal and top level framework.
Can we add Phero to the list? :) https://github.com/phero-hq/phero
-
If you haven't worked with TypeScript yet it's a good time to get started now. I prepared an intro that covers the most important points to React with TS. Including a few embedded exercises for you to practice.
You can use Phero. You can use it on your backend and frontend. It basically created a typed API from your backend afaik
garph
-
Best backend for GQL?
https://garph.dev is pretty good. I have been using it for two months and love the experience. I had started out with nexus and briefly also evaluted pothos but switched to garph because the dev experience was superior. It takes full advantage of the structural type system of typescript rather than frameworks that lean more towards java style idioms.
-
Ask HN: Who wants to be hired? (December 2023)
Location: EU, Germany
Remote: Yes
Willing to relocate: Yes
Technologies: HTML, CSS, TailwindCSS, JavaScript, TypeScript, Node.js, React/Next.js, Vue/Nuxt, GraphQL, REST, Postgres, Git, AWS, Docker + K8s
GitHub: https://github.com/mishushakov
LinkedIn: https://linkedin.com/in/mishushakov
Email: hey at mish.co
Most recently, I worked at Step CI a Technical Founder and authored the API-Testing Framework (https://stepci.com) and Garph (https://garph.dev), a full-stack API-Framework, which brings the developer-experience of tRPC to GraphQL.
My passion is in making tools developers love using and make them more productive.
-
tRPC โ Move Fast and Break Nothing. End-to-end typesafe APIs made easy
If you want something like tRPC but for GraphQL, you should definitely give Garph a try: https://garph.dev
-
I reviewed 1,000s of GraphQL vs. REST perspectives
Amazing findings! Really admire your effort here
Btw. If you're building a GraphQL API using TypeScript, you should take a look at garph (https://garph.dev) which helps you to create type-safe GraphQL APIs without code-gen
-
Next.js and GraphQL: The Perfect Combination for Full Stack Development
The next step is undoubtedly the creation of our GraphQL Schema using Garph to create a totally type-safe API without needing to do codegen.
- Garph - Fullstack Open-source GraphQL framework for TypeScript
- Garph - Fullstack Open-Source GraphQL framework for TypeScript
- Garph - Fullstack GraphQL framework for TypeScript
What are some alternatives?
protoc-gen-validate - Protocol Buffer Validation - Being replaced by github.com/bufbuild/protovalidate
zodios - typescript http client and server with zod validation
withtyped - ๐คน Type-safe RESTful framework for fullstack with all native implementation.
sonner - An opinionated toast component for React.
telefunc - Remote Functions. Instead of API.
ts-reset - A 'CSS reset' for TypeScript, improving types for common JavaScript API's
bash - Unofficial mirror of bash repository. Updated daily.
nuxt-scheduler - Create scheduled jobs with human readable time settings
jest-extended - Additional Jest matchers ๐๐ช
llm-client - LLMClient - JS/TS Use prompt signatures, Agents, Reasoning, Function calling, RAG and more. Based on the Stanford DSP Paper
Protobuf - Protocol Buffers - Google's data interchange format
suspense - Utilities for working with React Suspense