This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This is the core package for Envelop. You can find a complete documentation here: https://github.com/n1ru4l/envelop

This plugins adds simple LRU caching to your `validate`, to improve performance by caching the validation result.

This plugin tracks the complete execution flow, and reports metrics using Prometheus tracing (based on `prom-client`).

A NodeJS client for GraphQL Hive

Limit the depth allowed in a GraphQL query.

Limit the number of directives allowed in a GraphQL query.

Limit the number of aliases allowed in a GraphQL query.

Limit the number of tokens allowed in a GraphQL document.

- Skip the execution phase and reduce server load by caching execution results in-memory. - Customize cache entry time to live based on fields and types within the execution result. - Automatically invalidate the cache based on mutation selection sets. -

## Getting Started

This plugin collects errors and performance tracing for your execution flow, and reports it to [Sentry](https://sentry.io).

This plugin allows you to implement custom authentication flow by providing a custom user resolver based on the original HTTP request. The resolved user is injected into the GraphQL execution `context`, and you can use it in your resolvers to fetch the cu