Webpack (next.js): Critical dependency: the request of a dependency is an expression

[Ziothh]

Issue Summary

When switching the package manager of my monorepo from npm to pnpm I get this new error:

After a few hours of googling I had to park this issue. So I'm trying my luck here. Any help would be greatly appreciated!

 ⚠ ../../node_modules/.pnpm/@boxyhq+saml-jackson@1.26.7_@aws-sdk+client-sso-oidc@3.609.0/node_modules/@boxyhq/saml-jackson/dist/loadConnection.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
../../node_modules/.pnpm/@boxyhq+saml-jackson@1.26.7_@aws-sdk+client-sso-oidc@3.609.0/node_modules/@boxyhq/saml-jackson/dist/loadConnection.js
../../node_modules/.pnpm/@boxyhq+saml-jackson@1.26.7_@aws-sdk+client-sso-oidc@3.609.0/node_modules/@boxyhq/saml-jackson/dist/index.js
../api/src/app/saml/jackson.ts
../api/src/app/App.ts
../api/src/app/index.ts
../api/src/index.ts
../api/lib/server.ts
./src/features/auth/next-auth/server.ts
./src/app/[locale]/layout.tsx
Using engine: sql. Type: postgres

Steps to Reproduce

• Use pnpm
• dependencies:
  • next: v14.2.4
  • @boxyhq/saml-jackson: v1.26.7
  • @aws-sdk/client-sso-oidc: v3.609.0
  • webpack: v4.47.0 (not specified, but copied from pnpm-lock.yaml)

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

Technical details

• Browser version: Irrelevant
• Node.js version: v20.11.0
• OS: MacOS

[niwsa]

@Ziothh It should be safe to ignore as it's just a warning. Also you can try adding the specific dependecy to webpack ignore list here: https://github.com/boxyhq/jackson/blob/main/next.config.js#L22

[Ziothh]

@niwsa Thanks for the quick response. I copied that line of code into my project before but it didn't work. Probably because of the pnpm-specific module paths. I'll look into writing a matching regex expression.

One more question: Is there any way to make this log not appear when the creating controllers? Using engine: sql. Type: postgres

[niwsa]

Is there any way to make this log not appear when the creating controllers?

At the moment we don't have a way to disable the info log.

[Ziothh]

Would you guys be willing to add way to disable it in the config?

It took me a while to figure out where this log was coming from and it's bloating our logs with information we already know.

[niwsa]

@Ziothh Sure we can add a flag to control the logging. We will be making this change in one of the future releases soon.

[Ziothh]

Thanks a lot!