Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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