Stijn de Witt

At the risk of boring you, let me give you one extra reason for preferring tagged releases (maybe _the_ reason): Caching. Have a look at this article: [Best Practices for...

Cool!

Thanks for this contribution! I will review it soon

Thanks a lot Jirutka! This looks like great work! I have one question though... maybe we can improve it further by fixing anylogger so that export default can be used?...

@jirutka I added/changed some stuff, can you have a look? Now, when you run `npm test` it will actually try to compile new file `test.ts` and run the resulting js....

> Thus it works only when the library consumer enables esModuleInterop. Mmm I think my 'solution' has the same problem so not sure why I think I fixed anything 😓...

> This option just hides problems with wrong export/import declarations. Frankly, I'm not sure whether I agree with this. At least, I completely disagree with the decision by the ES6...

> For an npm package, export = is accurate if node -p 'require("foo")' works to import a module, and export default is accurate if node -p 'require("foo").default' works to import...

@akesling Your input is appreciated! > as long as you use CommonJS modules, esModuleInterop is necessary to prevent requiring the user to type import * as foo from 'bar'. Ok...

@akesling It is indeed very hard to have technical discussions and leave the ego at the door. I know I'm guilty as charged. I have a big-ass ego, sorry. But...