Q# Typescript is not using b8g they produce NPM Typescript broken stuff
The Current typescript builds are near none useful for anything as they use to much inheritance there exist many community projects which are also buggy that try to turn the API from Inside out into modules.
[ ] Make export = translate to exports default solves a lot of issues down the line
[ ] See above mentioned module Resolve errors same solution applies here use a bundler
[ ] Alternativ switch all to ESNext Typescript and create a extra package
[ ] Task: Create npm workspaces documentation including tsconfig.json reference linking and extend include exclude settings as also offer rollup compatible tooling to implement the first bundler based workaround to be more easy.
[ ] Make it more easy to run typescript anywhere integrate ts-node knowledge
[ ] #31
Collection of constraints to get a package.json typescript Stealify Lang Compatible package.
This List should empower people to design linters for packages to incremental make the compatible with them loadable on the web 4.0 as ECMAScript Modules while still allow it to get used by Buggy nodejs that depends on package.json.
This can be seen as some how hotfix for the NodeJS Bug.
Q# Typescript is not using b8g they produce NPM Typescript broken stuff The Current typescript builds are near none useful for anything as they use to much inheritance there exist many community projects which are also buggy that try to turn the API from Inside out into modules.
Collection of constraints to get a package.json typescript Stealify Lang Compatible package.
This List should empower people to design linters for packages to incremental make the compatible with them loadable on the web 4.0 as ECMAScript Modules while still allow it to get used by Buggy nodejs that depends on package.json.
This can be seen as some how hotfix for the NodeJS Bug.