| 05:24 | <Aapo Alasuutari> | Yeah, I was at least one of them. |
| 05:25 | <Jack Works> | what is that, default including re-export? |
| 05:25 | <Aapo Alasuutari> | My work schedule is chock-full with an impending release, but once that is done I'll try to get permission to work on that during office hours. |
| 05:26 | <Aapo Alasuutari> | Yeah. |
| 05:28 | <Aapo Alasuutari> | We had to set up "export all; import all as temp; export default temp.default || null;" kind of ugly workarounds because we needed a "synthetic redirect" from resource A to resource B without forcing B to be re-evaluated. |
| 05:29 | <Jack Works> | We had to set up "export all; import all as temp; export default temp.default || null;" kind of ugly workarounds because we needed a "synthetic redirect" from resource A to resource B without forcing B to be re-evaluated. |
| 05:29 | <Jack Works> | export * from 'x'; export { default } from 'x'; |
| 05:39 | <Aapo Alasuutari> | Except, that's a syntax error if 'x' doesn't have a default export. And if you're a CDN-like backend, you don't usually care to know if there is one or not. |
| 06:25 | <Jack Works> | In almost all cases I have handled, I know if the file has a default export or not. |
| 06:51 | <Aapo Alasuutari> | That is unfortunately not the case here. Some files are statically known, yes, but we also serve "generic" modules that we do not know the contents of. |