4 ms·

and how do you know whether or not for library X you need to import the default export or one of the named exports without looking at documentation? furthermore

and how do you know whether or not for library X you need to import the default export or one of the named exports without looking at documentation? furthermore, you have to remember which to use for every library because there's not a lot of consistency among libraries i think syntactically the destructuring syntax for imports is cool and clever, but in practice i find it annoying to use

lewisl9029 11y ago
For most of the libraries I've used so far, they generally seem to follow the convention of having the entire library in a single object as the default export while also exposing each individual function/property as named exports. In the case that they don't, I generally just try "import * as Foo" to find out exactly what the library exports. Not saying this is ideal, but it really isn't too bad either, in my opinion, considering the flexibility and conciseness this approach offers for the general case.