Jason Gore

Also running into this as an issue. I just had punycode randomly resolve to a 2.x version that was coincidentally installed by something else. This should be added as a...

This should absolutely result in a change in `safe-buffer` package. `buffer` should be declared as a dep by `safe-buffer` in its `package.json` if it requires it. I found this problem...

Since the spec defines meaning for the values I was looking for something more like: ``` declare const BUTTON_MAIN: 0; declare const BUTTON_MIDDLE: 1; declare const BUTTON_RIGHT: 2; ... ```

They can be present and work with certain browsers though without negative effects on other browsers though, right? I can understand the desire to remove these to have a common...

My statement that downlevel-dts doesn't support inline types was based on a conversation I had with Daniel, but it seems like that maybe [we were wrong](https://github.com/sandersn/downlevel-dts#type-modifiers-on-importexport-names-45). I still think the...

> Since "minor release" is often mentioned here, I'd like to add something. TypeScript does not follow semantic versioning. The version increment is always the same: Minor until 9, then...

> Sure -- previous TypeScript versions are available on npm, and you can install+run them to see if they "work" given whatever definition of "work" is operative in your environment....

>If CI speed is the most important thing, which it sounds like it is, then downlevel-dts is the fastest thing you can do here since it's parallelizable in the task...

That's what I've had to do for now, but these types of script entries are incompatible with npm. If users try to run `npm run build` in that package, it...

If there is the insistence on having overly detailed resolution output, I'm not sure why there is resistance to supporting customizable messages? It would allow the default behavior to persist...