You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.
Is it possible to remove the polyfill from default inclusion? Given the use of mjs it seems to assume some sort of bundling is happening anyway, so it seems reasonable to let users polyfill requestIdleCallback themselves as they see fit.
If you'd like, I am happy to make a PR with the removal and docs.
The text was updated successfully, but these errors were encountered:
I think that's a fair request. It probably makes the most sense to have a separate package that's just the requestIdleCallback and cancelIdleCallback polyfills, and then this package would have usage instructions indicating that users who want to support older browsers would need to include a polyfill (and suggest that separate package).
At the moment I suppose you could get this behavior using a bundler by aliasing the idle-callback-polyfills.mjs file to something of your choosing, but I agree it shouldn't necessarily require a bundler to make this happen.
Given the use of mjs it seems to assume some sort of bundling is happening anyway
Hmmm, not entirely sure what you mean by that. I was using .mjs just to signify that the source code was in ES module format (rather than CommonJS).
Is it possible to remove the polyfill from default inclusion? Given the use of
mjs
it seems to assume some sort of bundling is happening anyway, so it seems reasonable to let users polyfillrequestIdleCallback
themselves as they see fit.If you'd like, I am happy to make a PR with the removal and docs.
The text was updated successfully, but these errors were encountered: