Skip to content

dependency mismatch #6983

@elrumordelaluz

Description

@elrumordelaluz

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

  • 1. The issue provides a reproduction available on Github, Stackblitz or CodeSandbox

    Make sure to fork this template and run yarn generate in the terminal.

    Please make sure the GraphQL Tools package versions under package.json matches yours.

  • 2. A failing test has been provided
  • 3. A local solution has been provided
  • 4. A pull request is pending review

Describe the bug

After making no-breaking changes upgrade of packages of a project I am working on, I found that @graphql-tools/[email protected] which doesn't have yet @whatwg-node/promise-helpers as a dependency, for some reason is hoisted of resolving inside this package.

In my case is braking build in a server I can't upgrade yet the node version over 16, version is still supported by @graphql-tools.

Here is what I am getting witth yarn why @whatwg-node/promise-helpers:

=> Found "@whatwg-node/[email protected]"
info Reasons this module exists
   - "@graphql-tools#schema#@graphql-tools#utils" depends on it
   - Hoisted from "@graphql-tools#schema#@graphql-tools#utils#@whatwg-node#promise-helpers"
   - Hoisted from "@graphql-tools#schema#@graphql-tools#merge#@graphql-tools#utils#@whatwg-node#promise-helpers"
info Disk size without dependencies: "44KB"
info Disk size with unique dependencies: "172KB"
info Disk size with transitive dependencies: "172KB"
info Number of shared dependencies: 1

while in the package.json I have:

"@graphql-tools/schema": "10.0.16",
 "@graphql-tools/utils": "10.7.2",

both packages still supporting node@16.

Any idea on what could be the reason of this mismatch? Or if there is a way to use graphql-tools packages on node@16 while is supported but depending on another one which has set v18?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions