Ryan Cavanaugh

This error is correct given the information available to TS. See https://github.com/microsoft/TypeScript/wiki/FAQ#the-inferred-type-of-x-cannot-be-named-without-a-reference-to-y-this-is-likely-not-portable-a-type-annotation-is-necessary There's no reason to have `declaration` on in an eslint config so I would just turn it off

Like in the FAQ, you're talking about a package path `@eslint/core` that TS never "sees", thus has no ability to synthesize. You can see this in the error message -...

> (I have a large TypeScript project using composite for performance, and declaration cannot be disabled when composite is on.) Sure but why is your lint config part of your...

FWIW - this might or might not be a very difficult fix. Whether or not we preserve intermediate symbols during alias resolution is a bit of an implementation detail, so...

See https://github.com/Microsoft/TypeScript/wiki/FAQ#auto-import-heuristics-and-preferences

🤖 Thank you for your issue! I've done some analysis to help get you started. This response is automatically generated; feel free to 👍 or 👎 this comment according to...

> Reason: Object.assign() does accept primitives as a target, and it has its use, although awkward. There's a lot of text/screenshots here so maybe I missed it, but what *is*...

> `Object.assign(true, {})` returns `new Boolean(true)` OK, but why would you ever want that? All the code you're showing me here looks like code I wouldn't want to have.

I'm not really seeing a strong argument for changing this. Again it seems like the cases you want to be not-errors are cases that are very indicative of a likely...

Please open a new issue with repro if you're still seeing this. Thanks!