Kirk Waiblinger

#8869 has been merged now, so I'll work on this soon to open it up for review

@JoshuaKGoldberg Not quite yet. I have a branch on my machine which does that and incorporates #8869. Just need to clean it up slightly before pushing and undrafting.

@Eugeno Yes, the premature merge was a tad unfortunate. Was amended in https://github.com/typescript-eslint/typescript-eslint/pull/9174, which went in before the release, though, so the only impact should be a small handful of...

I think that this kind of implies having a separate loc for each reported import, too, for example ``` import { a, type b, c } from "outside-module"; ^ ^...

Has the idea of a non-contiguous loc for a single report been thought about before? That would allow us to get semantically sensible underlines but one fix... Would also make...

I think this rule is good to go into recommended-type-checked. Side conversations ongoing regarding the rule option, wrapping up shortly. There are IMO three open bugs that are blockers, though:...

@bradzacher @Josh-Cena @JoshuaKGoldberg ok! So, summarizing some side conversations, I _think_ the least common denominator that we've landed on now is that we can do strict-type-checked, but that we _do_...

Not much enthusiasm for this, and it was decided it's not going to be used as an enabler for #8667. Closed!

reopened a la https://github.com/typescript-eslint/typescript-eslint/issues/8667#issuecomment-2148569319

@rubiesonthesky > * runtime error (this is something that is saw, but I’m not sure if the exact circumstances why and how) 1. ReferenceError will (probably) occur in Brad's example....