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
If a module has both named exports and a default export
confusion increases
You can export the same thing as a named export and as a default export
if you want to increase clutter and confusion, sure why not?
If you used default export but then had to export another thing, you either have to use named exports together with a default export, or you have to change default export to a named export
if you love refactoring...
If declaration and default export are separate
good luck connecting the dots
Have to use .default in some cases (like with dynamic import())
You can accidentally use a different name in each import site
I don't blame you
The text was updated successfully, but these errors were encountered:
Reasons why default exports are evil:
.default
in some cases (like with dynamicimport()
)The text was updated successfully, but these errors were encountered: