graphql-zeus
json-schema-to-typescript
graphql-zeus | json-schema-to-typescript | |
---|---|---|
17 | 7 | |
1,896 | 2,791 | |
0.5% | - | |
4.3 | 7.2 | |
21 days ago | about 20 hours ago | |
TypeScript | TypeScript | |
MIT License | 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.
graphql-zeus
-
How to define schema once and have server code and client code typed? [Typescript]
When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.
-
Achieving end-to-end type safety in a modern JS GraphQL stack
You can think of GraphQL Zeus as Prisma for the frontend: it writes GraphQL queries out of JavaScript objects and produces the proper return types.
-
Recommendations for GraphQL and TypeScript?
graphql-zeus: You write your graphql queries using a JavaScript object like syntax. Looks cool, but I think it's too big of a burden on the team to have to give up writing queries using graphql-tag/gql.
- Schema-first development: which languages and libraries support it?
-
Graph-ql subscriptions without Apollo
https://github.com/graphql-editor/graphql-zeus generates subscription code and in generated code you'll find simple apiSubscription function you can use/copy
-
TRPC: End-to-end typesafe APIs made easy
You can do this with GraphQL too:
https://genql.vercel.app/
https://github.com/graphql-editor/graphql-zeus
I did a 5 min talk about these newer breeds of codegen tools (where it's a single client SDK that does automatic return type inference based on the input args), it's really neat:
https://www.youtube.com/watch?v=7n3MeMFHiMk
- GraphQL Zeus 4.0.0 – Autocomplete client for huuuuuge schemas like Hasura
- GraphQL Zeus 4.0.0 – Autocomplete client for huuuuuge schemas
json-schema-to-typescript
-
Gentle Introduction To Typescript Compiler API
Compile JSONSchema to TypeScript type declarations
-
Show HN: A tool to Convert JSON schemas into TypeScript classes
Nice! Lots of tricky edge cases to do this right: there’s ambiguity in the JSON Schema spec, version-to-version changes, many popular community conventions that don’t adhere to the spec, etc. Feel free to check out the tests to understand some of these: https://github.com/bcherny/json-schema-to-typescript (shameless plug — I have maintained this library for a number of years).
-
Why JSON Isn’t a Good Configuration Language (2018)
jsonnet is my go-to language for anything related to configuration, after having tried json, yaml, TS, edn, and tasting dhall and toml. It addresses all problems in the article and more.
the composition strikes a good balance between extensiveness and ease of use.
the generated json leads to easy and portable data, and if you write jsonschemas from jsonnet, tools like json-schema-to-typescript [1] make it easy to import a consistent interface, and almost every language has a reasonably up-to-date validation library.
[1] https://github.com/bcherny/json-schema-to-typescript
-
Show HN: Remult – a CRUD framework for full-stack TypeScript
Take a look at https://github.com/bcherny/json-schema-to-typescript, too. I used it successfully at a previous job. IIRC, I had to write some code to convert OpenAPI to JSON Schema but it wasn’t onerous
-
TRPC: End-to-end typesafe APIs made easy
If you're using OpenAPI, you could use this to generate TypeScript interfaces:
https://github.com/bcherny/json-schema-to-typescript
It works really well
-
Running Out of Heap Memory While Converting JSON Schemas - Not Understanding Heap Memory/Async/Await/Promises
I'm messing around with a process to convert JSON schemas to TypeScript interfaces using json-schema-to-typescript. I have a little under 900 JSON files each containing a schema, totaling about 3.5 MB.
-
I created a tool which automatically generates typescript definitions for API endpoints
json-schema-to-typescript
What are some alternatives?
trpc - 🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy.
MikroORM - TypeScript ORM for Node.js based on Data Mapper, Unit of Work and Identity Map patterns. Supports MongoDB, MySQL, MariaDB, MS SQL Server, PostgreSQL and SQLite/libSQL databases.
graphql-let - A webpack loader / babel-plugin / babel-plugin-macros / CLI / generated file manager of GraphQL code generator.
gqless - a GraphQL client without queries
json-schema-to-ts - Infer TS types from JSON schemas 📝
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
nestjs-openapi3 - OpenAPI 3.x document generation and serving for NestJS.
vscode-apollo-relay - Simple configuration of vscode-apollo for Relay projects.
nestjs-auth - Comprehensive handling of authentication and authorization for NestJS.
wundergraph-demo - This Repository demonstrates how to combine 7 APIs (4 Apollo Federation SubGraphs, 1 REST, 1 standalone GraphQL, 1 Mock) into one unified GraphQL API which is then securely exposed as a JSON API to a NextJS Frontend.
remult - Full-stack CRUD, simplified, with SSOT TypeScript entities