Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error: Option 'bundler' can only be used when 'module' is set to 'es2015' or later.

Open
#619 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, next.js, typescript
Domain
api, tooling

Research direction

Start by reproducing the failure with the provided create-next-app steps, the .graphclientrc.yml configuration, and npx graphclient build. Trace the GraphClient schema-generation path and its TypeScript module-resolution handling; done means the build succeeds with "moduleResolution": "bundler" without requiring users to switch to "node".

Written by the indexing model from the issue text.

Description

If I follow the steps of adding Graph Client to a fresh install of Next.js with TypeScript, running npx graphclient build yields the following output:

💡 GraphClient Cleaning existing artifacts
💡 GraphClient Reading the configuration
💡 GraphClient Generating the unified schema
💥 GraphClient - uniswapv2 Failed to generate the schema Error: Failed to fetch introspection from https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2: error TS5095: Option 'bundler' can only be used when 'module' is set to 'es2015' or later.

    at GraphQLHandler.getMeshSource (/Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/graphql/cjs/index.js:339:23)
    at async /Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:128:28
    at async Promise.allSettled (index 0)
    at async getMesh (/Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:123:5)
    at async Object.handler (/Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/cli/cjs/index.js:311:53)
💥 GraphClient Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh with DEBUG=1 environmental variable to get more verbose output.
    at getMesh (/Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:162:15)
    at async Object.handler (/Users/schmidsi/Development/@schmidsi/module-resolution-test/node_modules/@graphql-mesh/cli/cjs/index.js:311:53)

The error can be fixed with changing "moduleResolution" from "bundler" to "node". That being said, this might not be obvious for a lot of developers. Is it possible to make Graph Client work with "moduleResolution": "bundler"?

Steps to reproduce

hint: Content of graphclientrc.yml

npx create-next-app@latest
✔ What is your project named? … module-resolution-test
✔ Would you like to use TypeScript? … No / Yes
✔ Would you like to use ESLint? … No / Yes
✔ Would you like to use Tailwind CSS? … No / Yes
✔ Would you like to use `src/` directory? … No / Yes
✔ Would you like to use App Router? (recommended) … No / Yes
✔ Would you like to customize the default import alias (@/*)? … No / Yes
cd module-resolution-test
npm install --save-dev @graphprotocol/client-cli
touch .graphclientrc.yml 
npx graphclient build
Dominant language
TypeScript
Stars
186
Forks
49
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphprotocol/graph-client

All issues in graphprotocol/graph-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.