Disable unicorn/prefer-module in certain files

[jonahsnider]

Some tools don't currently support ECMAScript modules for configuration yet. For example, Prettier requires a JavaScript config to export an object with module.exports. The unicorn/prefer-module rule should be disabled for known configuration files that must use CommonJS.

Files to consider ignoring:

• .prettierrc.js
• .prettierrc.cjs
• prettier.config.js
• prettier.config.cjs
• next.config.js

[sindresorhus]

We can disable it for all .cjs files.

[jonahsnider]

I considered doing the same but some projects may use .cjs extensions in the source and still benefit from the warning.

[sindresorhus]

If you're using .cjs, you're intentionally opting out of ESM.

[fregante]

I think it should be ignored on

*.cjs
*.config.js
.*.js //if supported
!.any.config.that.we.know.supports.it.config.js

[sindresorhus]

@fregante Why complicate it? You can just use .cjs for those. It's only temporary anyway. Most tools will support ESM this year.

[fregante]

You can just use .cjs for those

Can you? The issue here is that tools don't yet fully support these changes. You can chose to let the user deal with it or you can avoid enforcing the rule for a few more months until tools catch up. Either way is ok for me.

[sindresorhus]

The tools I use support .cjs now, but PR welcome if you want to add a temporary override for the cases you mentioned.

[sindresorhus]

And the latest XO version ignores .cjs: https://github.com/sindresorhus/eslint-plugin-unicorn/releases/tag/v34.0.0

[fregante]

This leads me to believe that this issue can be closed as it's been resolved