There is still the flexibility to give other name; use 'as', which makes it very clear to reader that you are doing this
-
-
That might be true. I'm on huge TS stuff, where most modules also expose at least some interfaces around the main export
-
I've written nearly 100% TS modules for at least 2 years. I think when there is one JS export + interfaces default export is more valuable
-
I usually use default export as a way to indicate that the file you're importing from is really about one JS value indicated by its name.
End of conversation
New conversation -
-
-
I do think you mixing and matching styles a lot can be confusing but I think it's ok for npm packages to have default + named.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.