Ron Buckton

Apparently "correct" behavior when extending `null` is up for debate. The algorithms in the ECMA-262 specification related to `extends null` actually prevent it from working, and no engine currently supports...

We can possibly just change `__read` to do this: ```js __read = function (o, n) { var m = typeof Symbol === "function" && o[Symbol.iterator]; if (!m) return Array.prototype.slice.call(o, 0,...

Previously we didn't care about the `n` argument here since its purpose was to limit how many times we step through the iterator in cases like `[a, b] = [1,...

This was to support the following scenario: * You have both module and non-module (script) files in your TypeScript project * You specify both `--importHelpers` and `--noEmitHelpers` (or just `--noEmitHelpers`)...

If the issue is compelling enough, we could add a _tslib.global.js_ variant (similar to what we do for _tslib.es6.js_), and restrict _tslib.js_. However; that would be a breaking change if...

#42 does not entirely fix this issue.

NodeJS does not consider `tslib.es6.js` to be an ES Module because it has a `.js` extension. `tslib.es6.js` predates NodeJS's ESM support and wasn't really designed for it. NodeJS *does* treat...

Is this still an issue in Vite? I added a test locally using `vite` and it seems to import `tslib` just fine as is.

I've added a test for `[email protected]` in #172 and I'm not seeing the error that's being described in this issue. @schickling (or anyone else experiencing this), can you review the...

> If it helps, the use case that led me here was trying to work with [**Material Web Components**](https://github.com/material-components/material-web), in my case was just testing out **@material/mwc-button** and using ESM...