Bug: Typescript is not Written in Stealify and not using B8G Directly.

[lemanschik]

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
  • Re-exporting CJS module with export = from ESM via export * causes type error microsoft/TypeScript#51923
• https://github.com/microsoft/TypeScript/issues?q=is%3Aissue+is%3Aopen+moduleResolution Over 200 Open Issues. Each a core blocker Priority 0
  • Current workaround is to use a bundler to fix the resolve Errors.
  • --moduleResolution bundler (formerly known as hybrid) microsoft/TypeScript#51669
• Stealify Type System Related
  • Introduce mechanism for manipulating function types without losing generic type information microsoft/TypeScript#50481
• Documentation improvements for Typescript > Stealify Lang conversation
  • Establish, document and maintain a reference monorepo for building npm packages microsoft/TypeScript#51817
    • 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.
    • Should also when done send to marketing team to make the problems more visible as also add to other documentation that the problems can all be solved via https://github.com/lemanschik/why-you-should-switch-away-from-npm-nodejs
      • Related: Design a simple starter: why-you-should-switch-away-from-npm-nodejs#1
      • Make it more easy to run typescript anywhere integrate ts-node knowledge
        • Bug: ts-node is using NPM and Nodejs as is also Not Using Stealify Lang. #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.

• Bug: ts-node is using NPM and Nodejs as is also Not Using Stealify Lang. #31