Sindre mentioned this before. I wish that instead of creating a simple version of this, element-ready was simplified and instead a new "watch elements" package was created.
Some possible simplifications:
- drop timeout in favor of
signal: AbortSignal.timeout() - drop cache: I don’t think it's something that happens very often, it's probably 99% overhead.
memoize+many-keys-mapcan still be documented in the readme if people need it. - drop
stopin favor ofsignal.abort()
These changes would streamline the code considerably
sindresorhus / element-ready
Detect when an element is ready in the DOM
435
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too