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

Missing step to uncomment dotenv configuration

Open
#76 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
50/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
graphql, javascript, node.js

Research direction

Start in the production tutorial near the API key section and inspect server/src/index.js at line 1, where the dotenv configuration is referenced. Update the documentation to explain uncommenting that line and how dotenv supplies ENGINE_API_KEY so Apollo Engine metrics are sent; the tutorial should clearly acknowledge this setup.

Written by the indexing model from the issue text.

Description

We should mention somewhere around here that this line should be uncommented in order for dotenv configuration to take effect. Without this, metrics are not sent to Apollo Engine since the Apollo server does not actually have the ENGINE_API_KEY set. Also, some acknowledgement of how this works via the dotenv module seems like it would be appropriate.

Dominant language
TypeScript
Stars
1.2k
Forks
808
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 apollographql/fullstack-tutorial

All issues in apollographql/fullstack-tutorial

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.