Has anyone been getting TypeError: cache_localforage_1.default is not a constructor error?

[nikhilshrv-pdi]

• Created a new NestJS project and added a .meshrc.yml file.
• Made a graphql-mesh build by running yarn graphql-mesh build
• Made a node build by running yarn build
• Try running the build, getting error TypeError: cache_localforage_1.default is not a constructor

This is on latest version
"@graphql-mesh/cli": "^0.73.3",
"@graphql-mesh/graphql": "^0.28.0",

.meshrc.yml is

sources:
  - name: Countries
    handler:
      graphql:
        endpoint: https://countries.trevorblades.com

Shall I raise an issue for this?

[HermanVulkers]

I'm having the same error.

[ardatan]

So could you share a reproduction on CodeSandbox or StackBlitz please?

[HermanVulkers]

Unfortunately, I am not allowed to share the code. Is there perhaps anything you can deduct from the following log?

> kleine-grote-denkers@0.0.0 start:app
> nx run kleine-grote-denkers:serve


> kleine-grote-denkers@0.0.0 start:api
> nx run kleine-grote-denkers-api:serve


> nx run kleine-grote-denkers-api:serve


> nx run kleine-grote-denkers:serve:production

info  - Loaded env from apps/kleine-grote-denkers/.env.local
[ ready ] on http://localhost:4200
chunk (runtime: main) main.js (main) 4.66 KiB [entry] [rendered]
webpack compiled successfully (ed2ebbb03f7448ae)
Debugger listening on ws://localhost:9229/7ba1395b-d3d1-4311-a3e8-f57de9df791c
Debugger listening on ws://localhost:9229/7ba1395b-d3d1-4311-a3e8-f57de9df791c
For help, see: https://nodejs.org/en/docs/inspector
Persisted queries are enabled and are using an unbounded cache. Your server is vulnerable to denial of service attacks via memory exhaustion. Set `cache: "bounded"` or `persistedQueries: false` in your ApolloServer constructor, or see https://go.apollo.dev/s/cache-backends for other alternatives.
🚀  Server ready at http://localhost:4100/

> kleine-grote-denkers@0.0.0 mesh-prebuild
> mesh build --dir apps/kleine-grote-denkers-gateway/gateway

💡 🕸️  Mesh Cleaning existing artifacts
💡 🕸️  Mesh Reading the configuration
💡 🕸️  Mesh Generating the unified schema
(node:93019) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
💡 🕸️  Mesh Generating artifacts
💡 🕸️  Mesh Generating index file in TypeScript
💡 🕸️  Mesh Writing index.ts for ESM to the disk.
💡 🕸️  Mesh Writing index.ts for CJS to the disk.
💡 🕸️  Mesh Cleanup
💡 🕸️  Mesh Done! => /Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/apps/kleine-grote-denkers-gateway/gateway/.mesh

> kleine-grote-denkers@0.0.0 mesh-start
> mesh start --dir apps/kleine-grote-denkers-gateway/gateway

💥 🕸️  Mesh TypeError: cache_localforage_1.default is not a constructor
    at Object.<anonymous> (/Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/apps/kleine-grote-denkers-gateway/gateway/.mesh/index.ts:3280:15)
    at Generator.next (<anonymous>)
    at /Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/node_modules/tslib/tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/node_modules/tslib/tslib.js:114:16)
    at Object.getMeshOptions (/Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/apps/kleine-grote-denkers-gateway/gateway/.mesh/index.ts:48:20)
    at Object.handler (/Users/hermanvulkers/Development/humanoidsbv/kleine-grote-denkers/node_modules/@graphql-mesh/cli/bin.js:979:61)```

[ardatan]

We need a reproduction to see and debug the issue. Otherwise, I cannot help you.
Make sure all of your packages are up-to-date.

[DerStoffel]

Hi everyone,

I have the same issue and I created a stackblitz where it can be reproduced.

https://stackblitz.com/edit/nestjs-typescript-starter-4ra8j5

1. open the terminal and run npm run mesh:prebuild. This will create the .mesh folder on root level (ls -la in terminal to make sure it exists, it does not show up in the files section of stackblitz for reasons I do not understand)
2. run npm run mesh:start and you will see the error

💥 🕸️  Mesh TypeError: cache_localforage_1.default is not a constructor
    at Object.getMeshOptions (/home/proj...

I have found that error coming up when I tried to fire up nest itself. In src/app.module.ts you can see my effort of having mesh run in nest. Is that the way to do it?

I suspect the error is, that when you have a nest project the tsconfig runs with module: "commonjs" and target "es2017" while graphql-mesh wants to be run with module "esnext" and target "es2018".

That then generates a different way of instantiating cache.

Any idea on how to progress further here?

[DerStoffel]

Hi everyone,

TLDR: Add "esModuleInterop": true to your Nest projects tsconfig.json

I have played around a bit with it, and if I have read the sources correctly in ts-artifacts line 474 you can see the default ts compiler options.

Hence I tried to run a clean mesh project with the nest tsconfig which produced exactly that error.

To have successfully run yarn graphql-mesh start in the nestjs project I had to add "esModuleInterop": true to the tsconfig.json of the nest project.

I also managed to start up my nest project with the graphql-mesh integration as you can see in the stackblitz (still error state).

Cheers,
Chris

[Urigo]

By the way, for everyone here that uses NestJS, you can now use the better GraphQL Yoga server instead of Apollo Server thanks to our new integration of NestJS with GraphQL Yoga: https://www.graphql-yoga.com/docs/integrations/integration-with-nestjs

[DerStoffel]

Can also be seen in the stackblitz above :)

Btw. do you have a way of having resolvers for things like authentication also integrated with nestjs?

[Urigo]

super cool @DerStoffel !
Can you share more information about this question? (maybe in another discussion)
also, I would love to hear more about your experience with NestJS, how you use it with Mesh and why and general things that could be improved in both frameworks

[mnlbox]

@DerStoffel @Urigo did you manage to integrate Mesh with Nest.js, finally?
I have some difficulty doing that, I already asked my open questions here:
#5594