Our company enforces the 'no-default-export' rule across the codebase.
So while there is a single export from every file, it is a non-default named export.

Is there any way to use or adapt this library to check filename against non-default export?

I imagine expanding the match-exported rule applicability to files with exactly one non-default named export, continuing to ignore files that have multiple non-default exports.

If needed, to avoid breaking changes, this could be done as a configuration switch in the rule.