feat: making edge compatible

[morgs32]

Please don't take this too seriously. I wanted to make this compatible with nextjs middleware so I took a very brute force approach in my fork. I grabbed the bunchee build setup from the swr repo so as to not have to think at all about rollup. I used crypto-js for webhook verification (when there's probably a way to do it with crypto.subtle?). The sdk doesn't build if you have installed node_modules at the root. Altogether a lazy approach. Just putting it on your radar. Feel free to shake your head and close this!

[changeset-bot]

⚠️ No Changeset found

Latest commit: a6916ae

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[guillaumelachaud]

Hi!

It looks like there's a bunch of things that don't work anymore with regards to Github Actions and the repo's automation, that we will need to keep. I don't think we will be able to accept the PR as-is, but at least it puts the edge compatibility on our radar, thanks!

I have filed an issue internally to keep track of this and will have a look this week to get a sense of feasibility.