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

environment variables not working

Open
#643 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, typescript
Domain
cli, tooling

Research direction

Start with the README instructions and the .graphclientrc.yml configuration shown in the report, then reproduce the issue by running graphclient build with SUBGRAPH set in the shell. Trace how the endpoint's {env.SUBGRAPH} value is handled during the build and consider the work done when the variable is injected into the generated configuration.

Written by the indexing model from the issue text.

Description

If I follow the instructions in the readme and specify an env var like this in .graphclientrc.yml:

sources:
  - name: farther
    handler:
      graphql:
        endpoint: https://api.studio.thegraph.com/query/{env.SUBGRAPH}/version/latest

and then start the process with the following script: SUBGRAPH=<subgraph-id> graphclient build

...the variable doesn't get injected. Does anyone know why?

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.