Files
payloadcms/packages/eslint-plugin/customRules/no-jsx-import-statements.js
Alessio Gravili 1038e1c228 chore: move to eslint v9 (#7041)
- Upgrades eslint from v8 to v9
- Upgrades all other eslint packages. We will have to do a new
full-project lint, as new rules have been added
- Upgrades husky from v8 to v9
- Upgrades lint-staged from v14 to v15
- Moves the old .eslintrc.cjs file format to the new eslint.config.js
flat file format.

Previously, we were very specific regarding which rules are applied to
which files. Now that `extends` is no longer a thing, I have to use
deepMerge & imports instead.

This is rather uncommon and is not a documented pattern - e.g.
typescript-eslint docs want us to add the default typescript-eslint
rules to the top-level & then disable it in files using the
disable-typechecked config.

However, I hate this opt-out approach. The way I did it here adds a lot
of clarity as to which rules are applied to which files, and is pretty
easy to read. Much less black magic

## .eslintignore

These files are no longer supported (see
https://eslint.org/docs/latest/use/configure/migration-guide#ignoring-files).
I moved the entries to the ignores property in the eslint config. => one
less file in each package folder!
2024-07-09 09:50:37 -04:00

35 lines
769 B
JavaScript

/**
* Disallows imports from .jsx extensions. Auto-fixes to .js.
*/
/** @type {import('eslint').Rule.RuleModule} */
export const rule = {
meta: {
type: 'problem',
docs: {
description: 'Disallow imports from .jsx extensions',
},
fixable: 'code',
schema: [],
},
create: function (context) {
return {
ImportDeclaration(node) {
const importPath = node.source.value
if (!importPath.endsWith('.jsx')) return
context.report({
node: node.source,
message: 'JSX imports are invalid. Use .js instead.',
fix: (fixer) => {
return fixer.removeRange([node.source.range[1] - 2, node.source.range[1] - 1])
},
})
},
}
},
}
export default rule