Additionally, it separates binding languages from build languages: go, rust and assemblyscript are both; interfaces and typescript are bindings only and javascript is, currently, build only.
The reason for this is that we shouldn't need 2 different directories for JS and TS build strategies; because TS wraps are TS bindings + rollup.js config that produce a single JS file, that is then built as a JS wrap.
The reasons I built it this way are basically letting users tweak bundling configurations and debug their bundles freely, or even use other bundlers like webpack; and in general, not doing anything special or extra on our side for TS, but rather trying to get it as cheaply as possible on top of JS wraps
This PR adds:
Additionally, it separates binding languages from build languages: go, rust and assemblyscript are both; interfaces and typescript are bindings only and javascript is, currently, build only.
The reason for this is that we shouldn't need 2 different directories for JS and TS build strategies; because TS wraps are TS bindings + rollup.js config that produce a single JS file, that is then built as a JS wrap.
The reasons I built it this way are basically letting users tweak bundling configurations and debug their bundles freely, or even use other bundlers like webpack; and in general, not doing anything special or extra on our side for TS, but rather trying to get it as cheaply as possible on top of JS wraps