Longstanding issue #311 seems best addressed using a the Webpack build tool.
This may break imports with explicit paths! This is because Webpack packs all the code into a single (or small number) of downloadable bundles. This is a performance optimization, particularly for browser-based code. I'm still working on details, but by using output.libraryType = "umd" it generates Universal Module Definition file which can be consumed both from node.js and from browsers. This seems to cover a lot of ground.
Longstanding issue #311 seems best addressed using a the Webpack build tool.
This may break
import
s with explicit paths! This is because Webpack packs all the code into a single (or small number) of downloadable bundles. This is a performance optimization, particularly for browser-based code. I'm still working on details, but by usingoutput.libraryType = "umd"
it generates Universal Module Definition file which can be consumed both from node.js and from browsers. This seems to cover a lot of ground.Additional notes:
ts-loader