Détail du package

@graphql-mesh/cross-helpers

ardatan406.4kMIT0.4.10

Cross Platform Helpers for GraphQL Mesh

readme

Mesh GIF

Created by The guild

 

GraphQL Mesh

GraphQL Federation framework for any API
Go to documentation


npm version CI Discord Chat code style: prettier

GraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL services, such as REST and gRPC, and also databases such as MongoDB, MySQL, and PostgreSQL.

GraphQL Mesh allows you to use GraphQL query language to access data in remote APIs that don't run GraphQL (and also ones that do run GraphQL). It can be used as a gateway to other services or run as a local GraphQL schema that aggregates data from remote APIs.

The goal of GraphQL Mesh is to let developers easily access services that are written in other APIs specs (such as gRPC, OpenAPI/Swagger, OData, SOAP/WSDL, Apache Thrift, Mongoose, PostgreSQL, Neo4j, and also GraphQL) with GraphQL queries and mutations.

GraphQL Mesh gives the developer the ability to modify the output schemas, link types across schemas and merge schema types. You can even add custom GraphQL types and resolvers that fit your needs.

It allows developers to control the way they fetch data, and overcome issues related to backend implementation, legacy API services, chosen schema specification and non-typed APIs.

GraphQL Mesh is acting as a proxy to your data, and uses common libraries to wrap your existing API services. You can use this proxy locally in your service or application by running the GraphQL schema locally (with GraphQL execute), or you can deploy this as a gateway layer to your internal service.

How does it work?

The way GraphQL Mesh works is:

  1. Collect API schema specifications from services
  2. Create a runtime instance of fully-typed SDK for the services.
  3. Convert API specs to GraphQL schema
  4. Applies custom schema transformations and schema extensions
  5. Creates a Federation subgraph or a Federation-compatible supergraph

Getting started

Supported Source APIs

Schema Transformations

Contributions

Contributions, issues and feature requests are very welcome. If you are using this package and fixed a bug for yourself, please consider submitting a PR!

And if this is your first time contributing to this project, please do read our Contributor Workflow Guide before you get started off.

Code of Conduct

Help us keep GraphQL Mesh open and inclusive. Please read and follow our Code of Conduct as adopted from Contributor Covenant

License

GitHub license

MIT

changelog

@graphql-mesh/cross-helpers

0.4.10

Patch Changes

0.4.9

Patch Changes

0.4.8

Patch Changes

0.4.7

Patch Changes

0.4.6

Patch Changes

0.4.5

Patch Changes

0.4.4

Patch Changes

0.4.3

Patch Changes

0.4.2

Patch Changes

0.4.1

Patch Changes

0.4.0

Minor Changes

Patch Changes

0.3.4

Patch Changes

0.3.3

Patch Changes

0.3.2

Patch Changes

0.3.1

Patch Changes

0.3.0

Minor Changes

Patch Changes

0.2.10

Patch Changes

0.2.9

Patch Changes

0.2.8

Patch Changes

0.2.7

Patch Changes

0.2.6

Patch Changes

0.2.5

Patch Changes

0.2.4

Patch Changes

0.2.3

Patch Changes

0.2.2

Patch Changes

0.2.1

Patch Changes

0.2.0

Minor Changes

  • 0401c7617: Improvements on string interpolation ({env.sth} or {context.headers.sth}) for different environments

    As we mention in most of our docs, we usually expect a key-value header object in the context. But Fetch-like environments don't have this kind of object but instead Headers object which is a kind Map. Now Mesh can detect this and automatically convert it to the key-value object especially for Yoga users.

    Also Mesh now handles env in a better way for non-Node environments;

    Consider import.meta.env as env if available, else take globalThis as env.

0.1.7

Patch Changes

  • 12e1e5d72: Do not use index.js because esbuild doesn't pick the correct one in that case

0.1.6

Patch Changes

  • 3c0366d2c: - Support import.meta.env instead of process.env for browsers
    • Ponyfill util.inspect only if it is not Node env

0.1.5

Patch Changes

  • 974e703e2: Cleanup dependencies

0.1.4

Patch Changes

  • 55ad5ea44: Fix browser support

0.1.3

Patch Changes

  • 66b9b3ddc: Fixes for JSON handling and react native

0.1.2

Patch Changes

  • 7856f92d3: Bump all packages

0.1.1

Patch Changes

  • cf0836a64: fix: browser errors

0.1.0

Minor Changes

  • b2c537c2a: feat - cross-platform support