Rule that validates exports field

[mightyiam]

I have made a mistake specifying values of the exports field. I have used absolute paths. That doesn't seem to be valid. Would a rule regarding validity of the exports field be welcome?

[tclindner]

Most certainly! Are you interested in opening a PR?

[mightyiam]

Yes, please. Any special advice for this rule?

[dzearing]

I have some advice on things to validate for this rule:

• For each file path, validate the file exists
• For each path that has an "import" conditional, validate the source is ESM and not commonjs.
• For each path that has a "require" conditional, validate the source is commonjs and not esm.
• Validate invalid conditional situations (import and require are mutually exclusive, same with development vs production)
• For each path that has neither import or require conditions, validate that .js files match the module type specified in type, or if it is missing or not set to type="module", validate .js files are commonjs. (I think)
• If "types" are present in a dictionary, validate they are the first key (I read about this here; https://nodejs.org/api/packages.html#community-conditions-definitions)

I recognize this issue is pretty old but @mightyiam if you still have plans to implement this, hope this helps.

[DarthCoder117]

Sorry if I'm reviving an old issue, but I'd like to add onto the above suggestion.

If "types" are present in a dictionary, validate they are the first key (I read about this here; https://nodejs.org/api/packages.html#community-conditions-definitions)

Not only should "types" be first, but "default" should apparently also be last or else it breaks webpack.

Related issues on other repositories:

sondr3/radiant#3
euberdeveloper/dree#44
pixijs/pixijs#9691
vuetifyjs/vuetify#17436