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

graphql-playground-react@1.7.8 not found on cdn.jsdelivr.net

Open
#83 2 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
graphql, javascript, node.js, react, typescript

Research direction

Inspect the tutorial's server and client dependency manifests to find the Apollo package versions that produce the GraphQL Playground HTML. Verify the referenced jsDelivr assets resolve after the dependency update, then run the tutorial's existing checks or startup flow to confirm the playground loads.

Written by the indexing model from the issue text.

Description

Hey guys, thanks for the handy tutorial.

I've found an error running the Graphql Playground. The apollo-server-core@2.2.0-alpha.2 (apollo-server@2.2.0-alpha.2 dep) is setting the @apollographql/graphql-playground-react@1.7.8 version to 1.7.8, which doesn't exist anymore on the cdn.jsdelivr.net. Here's the playground html source:

<link rel="stylesheet" href="//cdn.jsdelivr.net/npm/@apollographql/graphql-playground-react@1.7.8/build/static/css/index.css" />
<link rel="shortcut icon" href="//cdn.jsdelivr.net/npm/@apollographql/graphql-playground-react@1.7.8/build/favicon.png" />
<script src="//cdn.jsdelivr.net/npm/@apollographql/graphql-playground-react@1.7.8/build/static/js/middleware.js"></script>

Updating apollo-server to it's current version 2.5.0 fixes the problem, as it changes the apollographql/graphql-playground-react version to 1.7.10.

I will send you guys a PR to update both server/client dependencies, if its ok.

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.