@ivan7237d@johnsoncodehk you can do reasonable “async signal” using something like Effect.ts’s `yield *` if it’s used to resume/restore the current observer after each promise resolves.
i also tried a babel plugin but it was quite slow adding a `maybeRestoreAsyncContext` around each `await`
@johnsoncodehk I guess with AsyncContext, there's still a problem that you can't re-run the part of an async function after one of the `await`s, only the whole function. Anyway, I've formalized my intuition into this library based on alien-signals, it was super fun: github.com/lazy-promise/l…
does anyone know of any good projects i can fund through a 501c3 that are art, culture, climate, welfare, education, economics (or secondarily anything that isn't ai policy or animal welfare)
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.