You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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)
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 theexports
field be welcome?The text was updated successfully, but these errors were encountered: