"Cannot find package '@graphql-mesh/transport-rest'" when running gateway package container

[blakel6819]

Description

Getting the following error running any of the 1.5.x gateway package containers when trying to load transport "rest":

• Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@graphql-mesh/transport-rest' imported from /node_modules/.chunk/unifiedGraphManager-DAEQW3BS.mjs

Can the @graphql-mesh/transport-rest package be included in gateway package container?
Or is there an alternative way to get this working?

Additional Context

I am defining a subgraph from an OpenAPI schema using @omnigraph/openapi package and following the GraphQL-Mesh docs.

The package is installed and is available in the node_modules directory, but it is not part of the container image.

Everything works as expected when running locally, but fails when running in Docker (locally and deployed).

If I try to import the package directly from the node_modules directory, I then encounter the following duplicate graphql modules error:

• Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results.
• https://github.com/ardatan/graphql-js/blob/master/src/jsutils/instanceOf.js#L27
• I have tried using resolutions in the pnpm package.json file as well

Environment

• @graphql-hive/gateway: ^1.5.x
• @graphql-mesh/compose-cli: ^1.2.x
• @omnigraph/openapi: ^0.108.x

[enisdenjo]

Not all transports are included in the docker image. You have to install it yourself. Please check the "Extend Docker Image" documentation on the how-to.

Your Dockerfile should roughly be:

FROM ghcr.io/graphql-hive/gateway
 
RUN npm i @graphql-mesh/transport-rest

[blakel6819]

Thanks for your reply @enisdenjo.

I have tried the suggestion, but still getting the following duplicate graphql modules error:

• Duplicate "graphql" modules cannot be used at the same time since different versions may have different capabilities and behavior. The data from one version used in the function from another could produce confusing and spurious results.
• https://github.com/ardatan/graphql-js/blob/master/src/jsutils/instanceOf.js#L27
• I have tried using resolutions in the pnpm package.json file as well

The repo I am working in is a monorepo using turborepo, could that be causing issues extending the docker image?

[ardatan]

But this command has nothing to do with your local setup;

RUN npm i @graphql-mesh/transport-rest

It installs the dependency inside the container.

Could you help us to reproduce your issue within a repo like this?
https://github.com/ardatan/docker-mesh-openapi-v1