graphql-mesh
lerna
graphql-mesh | lerna | |
---|---|---|
12 | 162 | |
3,170 | 35,389 | |
- | 0.2% | |
9.9 | 8.9 | |
3 days ago | 4 days 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-mesh
-
LlamaAcademy: Teach GPTs to understand API documentation with LoRA
I played with building out a graphql mesh [0] of a few different APIs as I was curious to see if I could build one schema (and subsets of it) and have GPT interface over that. Turns out, it did a pretty good job if you can provide it the right portions of the schema it needs.
It also helped out when I was struggling to reconcile with how large of JSON payloads I was getting. The REST endpoints are just killing the prompt size, but having the model choose the fields it needed from GraphQL really helped out there.
Put it down for a while until I can get access to the plugin fine-tuned version of chatgpt and see if there's still a need or if it is additive still.
[0] https://github.com/Urigo/graphql-mesh/
-
Uncovering Frontend Data Aggregation: Our Encounter with BFF, GraphQL, and Hydration
graphql-mesh is a tool that allows you to integrate backend microservices (whether they are REST with OpenAPI specs, GraphQL, etc.) into a single GraphQL Gateway. It's easy to set up as it generates schemas, queries, and mutations based on the provided specifications. You only need to implement additional properties for data aggregation
-
Are there any good GraphQL "passthrough" solutions?
You might be able to integrate existing API's with https://www.graphql-mesh.com/ but keep in mind this will add latency and you won't get all the full benefits of implementing native graphql services.
- Show HN: M3O – Universal Public API Interface
-
How not to learn GraphQL
Recent projects such as GraphQL Mesh or products such as Hasura Cloud proved that GraphQL has a purpose beyond the simple front-end/mobile apps fetching challenges.
-
Join multiple GraphQL APIs without Schema Stitching or Federation
I’ve seen more products letting you join/merge GraphQL schemas independent of schema stitching or federation. Have a look at GraphQL Mesh or StepZen.
-
Improving microservice architecture with GraphQL API gateways
Libraries like GraphQL Mesh, on the other hand, automatically stitch multiple data sources into one single GraphQL API. This can save development time, but, like libraries that do a lot for you, you may need to provide custom overrides.
-
GraphQL Mesh as a Gateway | Episode #1
GraphQL Mesh acts as a proxy to your existing APIs, and gives you the developer ultimate control over how data is retrieved. It doesn't matter if your API is GraphQL, gRPC, Swagger, Postgres, and non-typed APIs. GraphQL Mesh can figure out how to transform your GraphQL query to the respective API.
-
Making Open Source Easy - Orchestrating the Open Source Contribution Workflow
Doing this was pretty simple. You can find the repo here which is used as the master repository to push all the labels downstream and we still retain the repo specific labels in their own repository (like this)
-
Webhooks as GraphQL Subscriptions using GraphQL Mesh
You can find a complete working example on GitHub
lerna
-
Add Step-up Authentication Using Angular and NestJS
Open the project up in your favorite IDE. Let's take a quick look at the project organization. The project has an Angular frontend and NestJS API backend housed in a Lerna monorepo. If you are curious about how to recreate the project, check out the repo's README file. I'll include all the npx commands, CLI commands, and the manual steps used to create the project.
-
Things I learned while building projects with NX
Lerna currently maintained by Nx team
- tsParticles 3.0.0 is out. Breaking changes ahead.
-
Nx 16.8 Release!!!
On Netlify's enterprise tier, approximately 46% of builds are monorepos, with the majority leveraging Nx and Lerna. Recognizing this trend, Netlify has focused on enhancing the setup and deployment experiences for monorepo projects. In particular they worked on an "automatic monorepo detection" feature. When you connect your project to GitHub, Netlify automatically detects if it's part of a monorepo, reads the relevant settings, and pre-configures your project. This eliminates the need for manual setup. This feature also extends to local development via the Netlify CLI.
- Mocha/Chai with TypeScript (2023 update)
-
Help with library implementation in a big webapp
This is the exact problem monorepos were born to solve. Not only will a monorepo let you share UI components, you'll be able to gradually add shared application logic as well (for instance, do all of your apps have their own logic for connecting to a database? you could roll that into a shared library with a monorepo). There are a lot of tools for accomplishing this in JS, but probably the most popular is lerna, which is built on top of NX (though lots of teams roll their own monorepo in nx without lerna, which IMO is a totally valid option).
-
How to Build and Publish Your First React NPM Package
To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.
-
Utility for making sure that I'm using the right `@types/react`
If so, are you using a monorepo tool like Nx or Lerna? If not, start there and see if it solves your problem.
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references
-
Understanding npm Versioning
Tools for publishing, such as Lerna (when using the --conventional-commit flag), follow this convention when incrementing package versions and generating changelog files.
What are some alternatives?
apollo-server - 🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
mercurius - Implement GraphQL servers and gateways with Fastify
nx - Smart Monorepos · Fast CI
openapi-to-graphql - Translate APIs described by OpenAPI Specifications (OAS) into GraphQL
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
graphql-transform-federation - Convert your existing GraphQL schema into a federated schema
pnpm - Fast, disk space efficient package manager
apollo-angular - A fully-featured, production ready caching GraphQL client for Angular and every GraphQL server 🎁
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
single-spa - The router for easy microfrontends