| 05:05 | <Jack Works> | I want to do a temperature check: do you think this is a problem worth solving? if the module includes async dependencies, it might miss some startup event in some environments (e.g. onInstall in web extensions, we really hit that problem in the past). Proposal :add a new directive or something, to assert the module has no async dependencies. if assert failed, it will fail the whole graph. Fail-fast can help to find the bug early. "asserts sync"; |
| 05:38 | <ljharb> | so basically, a way to prevent someone adding TLA in one of your deps? i asked for this iirc during TLA at one point, and i love the idea - otherwise you’d need an expensive lint rule to find it. |
| 06:16 | <Rob Palmer> | So this is a pragma that is an early error? |
| 06:46 | <bakkot> | I think the ideal form would be like `with { forbidAwait: true }` or something, in an import |
| 06:46 | <bakkot> | Though I guess it would be annoying to have to put it in all of them |
| 06:47 | <bakkot> | Seems like a problem space worth investigating at least |
| 22:54 | <Jack Works> | yes, my first iteration is using import assertions, but now it's no longer an assertion |
| 22:56 | <Jack Works> | and when you add it, you do not want to add it to some dependencies and some not, so a new pragma is the best solution I can think so far |
| 22:56 | <Jack Works> | but the committee doesn't like adding a new pragma IMO? |