eliasm307

Note the original issue (that I raised) was just for `override` modifier support, but I also realised `async` modifier support was missing so did it as part of this as...

Hi @JoshuaKGoldberg yeah I've been thinking about this recently but I haven't had a moment to apply the feedback. I'm busy this weekend but might have a look next weekend

> Ping @eliasm307 - do you still have time to work on this? No worries if not, just don't want it pending too long. 🙂 @JoshuaKGoldberg Thanks for the feedback!...

> > involves JS code which cant be emulated in playground at the moment > > The playground supports JS. Cool didnt know that! Still cant use it for this...

> Please provide necessary code as text when it appears in a screenshot @RyanCavanaugh See code below from the different files. tsconfig with `allowJs=true` on and `checkJs=false` ie default: ```jsonc...

Im having the same issue

> Got the same issue here, with Next v14. Downgrading to Next v13.4.19 solves the issue for now. This worked for me as a stop gap

@JoshuaKGoldberg cool! So from the title mentioning "nodes" specifically, can I confirm if this rule is meant to be specific to the typescript-eslint/eslint code bases? Could have a general "no-in"...

Ah ok, in that case it sounds technically interesting. Assuming it's a rule with auto fixing, it might be challenging sometimes to be able to determine what predicates an "in"...

 A similar package `vega-loader` manages to get its licence content included, so not sure if its an issue with the plugin or the package's distribution however they look similar...