Pull in filenames/match-exported

[graingert]

// Considered problem only if the file isn't named foo.js or foo/index.js 
export default function foo() {}
 
// Considered problem only if the file isn't named Foo.js or Foo/index.js 
module.exports = class Foo() {}
 
// Considered problem only if the file isn't named someVariable.js or someVariable/index.js 
module.exports = someVariable;
 
// Never considered a problem 
export default { foo: "bar" };

https://www.npmjs.com/package/eslint-plugin-filenames#matching-exported-values-match-exported

[ljharb]

Due to eslint limitations with shared configs, this will sadly add another peer dependency for both eslint-config-airbnb-base and eslint-config-airbnb.

That said, this is a good rule that I think we should indeed add, but I'd like to test out the plugin on our codebase before adding it here.

[graingert]

@ljharb agreed

[graingert]

@ljharb any chance to look at this?

[ljharb]

I haven't had a chance to test it out yet; but in general i'm pretty loath to ever add another peer dependency.