Setting up @envelop/response-cache-redis for use in RedwoodJS application

[JrobT]

Hi

Apologies if this is not the appropriate place to ask!

I'm sure I'm doing something silly or the issue is specific to my project, but I'm stuck on implementing useResponseCache in my GraphQL handler in the API of my RedwoodJS application.

I've been trying to follow this tutorial: https://community.redwoodjs.com/t/guide-power-of-graphql-caching/2624.

My GraphQL handler looks like this:

...
const extraPlugins = [useResponseCache({ cache, session: () => null })]
...
export const handler = createGraphQLHandler({
  allowIntrospection: API_ONLY,
  authDecoder,
  ...cors,
  directives,
  extraPlugins,
  getCurrentUser,
  loggerConfig,
  onException,
  sdls,
  services,
})

When I run my application, I get the error:

🚨 TypeError Info
[1] api | 
[1] api | {}
[1] api |  
[1] api | 🥞 Error Stack
[1] api | 
[1] api | TypeError: (0 , core_1.getDocumentString) is not a function
[1] api |     at defaultGetDocumentString (/Users/<myname>/code/<app>/node_modules/@envelop/response-cache/cjs/plugin.js:40:41)
[1] api |     at onExecute (/Users/<myname>/code/<app>/node_modules/@envelop/response-cache/cjs/plugin.js:229:33)
[1] api |     at /Users/<myname>/code/<app>/node_modules/@envelop/core/cjs/orchestrator.js:347:37

Does anyone have an idea on what the issue is?

[JrobT]

Issue was that I needed to install @envelop/core myself.

[EmrysMyrddin]

Yes, @envelop/core is a peer dependency, so you need to actually install it yourself. This is to avoid having multiple envelop core versions in the same app, which can lead to some very very difficult to debug issues.