Rule Proposal: exports-last

[k15a]

I would like to propose a new rule which enforces that all export statements are at the end of the file.

Why?

I really like to keep all my exports at the end of the file so I can quickly scan what a file exports.

[jfmengels]

Sounds good to me.
With commonjs, I have the same preference. I don't necessarily have it for ES6 modules at the moment, but this makes sense to me to have this rule.

@k15a Would you be interested in working on this if it gets accepted? :)

[k15a]

I am interested but I tried working on another issue 2 times and failed hard so it's not a guarantee for success 😆

[benmosher]

Sounds like a reasonable style guide rule to me. 👍

[sevor005]

Good afternoon! The question is: can I cancel the rule (put it in ignor) for classes that are exported at the beginning of the file export default class SomeClass, followed by defaultProps and PropTypes?

[ljharb]

no. Class fields exists, define them inside the class body.

[RodrigoNovais]

Good afternoon! The question is: can I cancel the rule (put it in ignor) for classes that are exported at the beginning of the file export default class SomeClass, followed by defaultProps and PropTypes?

This would be reasonable for storybook csf files, since templating would require exports to be mixed within the file
It's not a big deal to disable the rule on every stories file but would be nice to be able to handle it in the eslint config

[ljharb]

@RodrigoNovais you can use overrides to disable them on every story file at once, in the config.

[RodrigoNovais]

Didn't know that's possible, thank you @ljharb