| 02:53 | <Jack Works> | But deep importing is discouraged by the npm ecosystem by "export map", you have to explicitly expose the folder you want to (when using export map) |
| 04:07 | <ljharb> | how is that discouraging it? |
| 04:08 | <ljharb> | it certainly means your "exports" needs to enumerate all your entry points, sure |
| 04:08 | <ljharb> | but it means users have much smaller bundle sizes and/or memory footprints, way smaller than "treeshaking" can achieve |
| 04:53 | <Kris Kowal> | It would be fair to say that export maps tilt the field slightly away from accidental deep exports in a way that gives package authors an important degree of control over the expression of their forward compatibility commitments, but I would not say it discourages deep exports. |
| 06:33 | <ljharb> | you have to explicitly add a . also, and explicitly make your barrel/manifest file, so it seems the same to me as far as maintainer effort |
| 16:48 | <annevk> | littledan: are we meeting today? Not a lot of people confirmed for today. |
| 16:57 | <nicolo-ribaudo> | I will join |
| 16:57 | <guybedford> | annevk: these meetings have been fairly regular so I'm sure a few of us will turn up |
| 16:57 | <guybedford> | as long as we have someone with the permissions that is... |
| 16:57 | <Kris Kowal> | All set to welcome folks into the meet. |
| 17:04 | <Kris Kowal> | littledan we have anne today. Any chance you’re on your way? |
| 18:49 | <annevk> | My follow-up from the meeting: https://github.com/whatwg/html/issues/7233#issuecomment-1385852355 I will have more Jan 26 as part of the group meets then |
| 19:16 | <littledan> | ah sorry for missing the meeting, but I'm glad to hear that Anne got to meet everyone |