Connor Shea
Connor Shea
This _should_ be resolved now with the released packages.
See also #14602, I'm not sure which is the best to go with as the solution here but I definitely think we need to prioritize fixing this rule.
Also this issue #12220, which I think this PR would solve?
Yeah I think this is important to fix for consistency, especially in preventing unintended differences between CI envs and local developer envs, if they use different shells.
Hm, it's a bit confusing to mark the rules as `no need to implement`, unless the intention is never to support linting code inside `` tags at all. Is that...
My two cents: this makes it a lot more complex to configure the linter with jsPlugins and just generally has the potential to really easily have users screw up their...
the airbnb config sets `mjs` as a default value as well, so this is probably very common: https://github.com/airbnb/javascript/blob/0e2ef178a26ba9ac3495402a182891ad8096d3a0/packages/eslint-config-airbnb-base/rules/imports.js#L142
hmm, maybe `.vue`, `.astro`, `.svelte`, and `.css` as well? And/or an escape hatch for "all other problematic cases? e.g. right now if you have this set to never allow extensions:...
This will be fixed by #14602
Doing this will involve modifying [the code here](https://github.com/oxc-project/oxc/blob/6faa11d73cbe58c33941acbfef3c6940a696d572/tasks/website/src/linter/rules/doc_page.rs#L144-L148), I believe. Not just that location, but that'll be part of it at least.