import Foo from "./foo" What if, inside foo.js you rename class Foo to class Bar Old imports will still work w/ old name: they no like
1: import extend from "extend" is enough convention (and is lintable) to get this benefit if you want.
-
-
2: you don't *also* have to enforce yet another copy of the name at the definition site.
-
3: the way to think about it imo is that the name of the default export is the name of the module, so it was already named.
-
4: import assign from "extend" can be seen as quite funny-looking (just like renames) and again can be linted.
-
5: In practice, there are large codebases with one-class-per-module that benefit a lot from the simplicity of using the module as ...
-
6/6: the identity of the class rather than the module + a name (which ends up needing a convention anyway to avoid eye-stabbing)
End of conversation
New conversation -
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.