Vladyslav Zubko

Hello, guys! Do you have any news on this? I think it's no secret that `type="module"` is becoming more prevalent. It would be nice to allow the `.cjs` extension at...

> you're probably right that we should just mark CEs as used when passed through the customElement decorator > > since it is lit-specific knowledge/side-effects, it seems to make sense...

> i had a think about this, its a bit of an awkward one for us to solve > > basically, multiple rules work against lit classes conditionally (i.e. `if...

> that makes sense in their case as they have a rule for detecting those types > > we don't really have a rule whose purpose is to detect registered...

Hey @43081j Sorry for the delayed response! I understand you, and it seems that indeed, if we add a new rule, it will simply mark classes as used, and nothing...

> With #1098 now dropping `jsdoc/no-undefined-types` from the recommended rules for typescript configs (including a new config `recommended-typescript-flavor` for plain JavaScript), and with TypeScript handling this properly, I think we...

Agreed. Will be looking forward to this rule. Or, if anyone has snippets for `no-restricted-import` that would be nice too 🙏 (but the new rule would be simpler 😁). I...

All node documentation uses prefixed imports. Since it becomes the standard why keep two ways of importing? I think this rule would help with that.

Additional points: https://github.com/nodejs/node/issues/38343 Btw, the PR has a rule for forcing the use of the `node:` protocol. But this is part of the unicorn eslint plugin. I think many people...

more and more people will ask for it 🙂 https://github.com/goldbergyoni/nodebestpractices#-627-import-built-in-modules-using-the-node-protocol