Closed wKich closed 2 months ago
Latest commit: 90ba86e2215da6bc89ec773b6c4949307b2f2951
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.
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
Name | Link |
---|---|
Latest commit | 90ba86e2215da6bc89ec773b6c4949307b2f2951 |
Latest deploy log | https://app.netlify.com/sites/interactors/deploys/66d5c03632e9310008637815 |
Motivation
In #264 we are adding
@interactors/cli
pacakge, which allows you to build interactors agent for injecting interactors in different environments and control them from outside. We'd like to distribute the CLI as a deps-free executable. But unfortunately there is no way to do it with node, even with SEA feature, because of esbuild, which can't be bundled. Hopefully in Deno there is esbuild package which downloads its binary in runtime and we can compile CLI executableApproach
Migrate from Yarn monorepo to Deno workspace
Possible Drawbacks or Risks
I think we have to cut some pieces, like stories in material-ui interactors or maybe remove them completely, because they were made for the old mui version. Also remove sample app, which hasn't been updated quite long time
TODOs and Open Questions
Move from npm binaries to deno task scripts, because deno doesn't download npm packages if they aren't used in code(It doesn't work)typedoc
todeno doc