Currently, the import/prefer-default-export rule from eslint-plugin-import is being used. This rules enforces a default (versus named) export when only one thing is exported from a module.
There are good arguments to use named exports instead of default exports, like the ones explained in this document or in this post.
What has been done
Summary: the prefer default export requirement has been inverted, now all exports must be named.
Commits:
Replace the import/prefer-default-export rule with import/no-default-export in the .eslintrc.json file.
Disable the new rule in the vue component type definition.
Replace all default exports with named exports.
Add this change to the changelog
In particular you have to check
The rule disabling in the vue component type definition. Maybe I should ignore the rule in a different way, like using overrides in the .eslintrc.json file.
Additional info (screenshots, links, sources, etc.)
Context
Currently, the
import/prefer-default-exportrule from eslint-plugin-import is being used. This rules enforces a default (versus named) export when only one thing is exported from a module.There are good arguments to use named exports instead of default exports, like the ones explained in this document or in this post.
What has been done
Summary: the prefer default export requirement has been inverted, now all exports must be named.
Commits:
import/prefer-default-exportrule withimport/no-default-exportin the.eslintrc.jsonfile.In particular you have to check
The rule disabling in the vue component type definition. Maybe I should ignore the rule in a different way, like using overrides in the
.eslintrc.jsonfile.Additional info (screenshots, links, sources, etc.)