🧑‍💻 Migrate to Deno for development

[cowboyd]

Motivation

There are two main reasons that we want to migrate to Deno:

1. The TS types that we currently ship with our interactors packages are broken, and rather than maintain and build the npm packages by hand, we can just use DNT to build them for us knowing that they'll be maximally compatible with NPM going forward.
2. We're planning on using Deno to build the interactors CLI, so it would be nice to have that in place first.

Approach

Migrate to a single Deno workspace, and then use covector for change management and publication. Releases will represented via a tag, and then publication to package registries can happen independently.

Shout out to @wKich for doing the heavy lifting on this!

[netlify[bot]]

✅ Deploy Preview for interactors canceled.

Name	Link
🔨 Latest commit	430a6782224e679def380498561305023a63790c
🔍 Latest deploy log	https://app.netlify.com/sites/interactors/deploys/66e8f24e4698480008347715

[github-actions[bot]]

Package Changes Through 430a6782224e679def380498561305023a63790c

No changes.

Add a change file through the GitHub UI by following this link.

---

Read about change files or the docs at github.com/jbolda/covector