graphql-middleware
graphql-middleware copied to clipboard
dimatill
Split up your GraphQL resolvers in middleware functions
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.226.1 to 2.1036.0. Release notes Sourced from aws-sdk's releases. Release v2.1036.0 See changelog for more information. Release v2.1035.0 See changelog for more information. Release v2.1034.0 See changelog...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [aws-sdk](https://github.com/aws/aws-sdk-js) from 2.226.1 to 2.1030.0. Release notes Sourced from aws-sdk's releases. Release v2.1030.0 See changelog for more information. Release v2.1029.0 See changelog for more information. Release v2.1028.0 See changelog...
Bumps [object-path](https://github.com/mariocasciaro/object-path) from 0.11.5 to 0.11.8. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
Bumps [object-path](https://github.com/mariocasciaro/object-path) from 0.11.5 to 0.11.8. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
Unless I've missed something, I don't think it's supported: It would be great to handle wildcard middlewares as in [graphql-shield](https://github.com/maticzav/graphql-shield#per-type-wildcard-rule).
Some javascript bundlers use `require.resolve` to identify the `package.json`. If the `package.json` can't be resolved, the dependency isn't included. Specifically in my case, [generate-package-json-webpack-plugin](https://github.com/lostpebble/generate-package-json-webpack-plugin/blob/master/index.js#L101) was having trouble locating the `package.json`...
Currently `graphql-middleware` uses `@graphql-tools/schema` package to actually apply schema modifications to the initially provided one (via `addResolversToSchema` function). Here https://github.com/maticzav/graphql-middleware/blob/8dc4590a421feff4a1455b1cf672cb10798c66c8/src/middleware.ts#L45 it hard-codes `addResolversToSchema` to always produce a new schema. I'd...
We are experiencing very high memory usage when we add even a noop middleware to our express Apollo GraphQL application. Do we have an idea of what memory / CPU...
Hello ! I have the following resolvers, (schema created with `makeExecutableSchema`) ```{Javascript} const resolvers = { Muation: { viewerMutation: (_, args, context) => { book: () => { author: ({id})...
