node-fetch package is not being correctly tracked as a dependency

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Just noticed that although node-fetch is being used in a couple places in the project, it's not actually defined in any of our package.json's! 😱

Details

Basically, if you look at the output from Yarn, it looks like we've gotten luck that it has come in through other dependencies, but we should really track it since those deps could change at any time.

% yarn why node-fetch
yarn why v1.22.5
[1/4] 🤔  Why do we have the module "node-fetch"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found "node-fetch@2.6.1"
info Reasons this module exists
   - "_project_#@greenwood#cli#puppeteer" depends on it
   - Hoisted from "_project_#@greenwood#cli#puppeteer#node-fetch"
   - Hoisted from "_project_#lerna#@lerna#version#@lerna#gitlab-client#node-fetch"
   - Hoisted from "_project_#@greenwood#plugin-graphql#apollo-server#apollo-server-core#apollo-server-env#node-fetch"
   - Hoisted from "_project_#@greenwood#plugin-graphql#apollo-server#apollo-server-core#@apollographql#apollo-tools#apollo-env#node-fetch"
   - Hoisted from "_project_#lerna#@lerna#version#@lerna#github-client#@octokit#rest#@octokit#request#node-fetch"
info Disk size without dependencies: "180KB"
info Disk size with unique dependencies: "180KB"
info Disk size with transitive dependencies: "180KB"
info Number of shared dependencies: 0
✨  Done in 0.97s.

Unfortunately, NodeJS doesn't have an implementation of the Fetch API natively (nodejs/node#19393) 😢