Remove node-fetch by default

[gr2m]

Node 18 comes with a global fetch built-in. Node 14 will be out of maintenance end of April 2023, and Node 16 on a few months later on Sep 11. Node 18 is already the current stable release today.

Using node-fetch is a continuous pain point. Using ESM and conditional exports might help, but I think we should do a clean cut instead.

Adding node-fetch is fairly simple anyway.

Instead of

import { Octokit } from "octokit"
const octokit = new Octokit()

Developers will need to do

import { Octokit } from "octokit"
import fetch from "node-fetch"
const octokit = new Octokit({ request: { fetch } })

We can also throw a helpful error in case a global fetch is not defined, specific to the runtime environment.

[github-actions]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀