fix(build): switch to esbuild in place of pika

[kfcampbell]

Replicating octokit/request.js#584 to another repo.

---

Pika has been deprecated for a while now, and the project has now been archived, and because of that the released npm package is missing most of the files generated by the build step.

Uses esbuild to transpile the TS source code into an ESM source, NodeJs bundle, and a browser bundle

Uses the TypeScript compiler to generate the types.

Behavior

Before the change?

• Uses pika for the build system
• The released npm package is missing most of the files generated by the build step. dist-node, dist-types, dist-web... even though they are generated correctly.

After the change?

• Uses esbuild to generate the JS bundles
• Uses the TypeScript compiler to generate the type definitions
• The correct file matching patterns are used so we publish all the necessary files again.

---

Additional info

Pull request checklist

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes (Please add the Type: Breaking change label)
• No

If Yes, what's the impact:

• N/A

Pull request type

Please add the corresponding label for change this PR introduces:

• Bugfix: Type: Bug
• Dependencies/code cleanup: Type: Maintenance

---

[wolfy1339]

You forgot to remove the pika key from package.json

[kfcampbell]

Good catch. Done!

[kfcampbell]

I imagine the pika CDN references can stay, correct?

[wolfy1339]

Yep those references can stay, for now.

[github-actions]

🎉 This PR is included in version 2.0.5 🎉

The release is available on:

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

Your semantic-release bot 📦🚀