Do not include polyfill

[unindented]

Including the ResizeObserver polyfill makes this module unnecessarily heavy. Apps should be lazy-loading polyfills, so that they don't ship unnecessary code to modern browsers.

Would you consider shipping this module (or a version of this module) without the polyfill?

[d6u]

Sorry for the late reply, sounds like a good idea. I will find some time for this maybe this weekend. Also PR is welcome.

[unindented]

@d6u we can create a PR, with a bit of guidance... How would you go about it? Would you remove the dependency on resize-observer-lite completely?

[swese44]

react-container-query uses resize-observer-lite to listen to change events to re-render the react component tree:
https://github.com/d6u/react-container-query/blob/master/src/ContainerQueryCore.ts#L11

resize-observer-lite prefers to use the browser's window.ResizeObserver directly, but if not present will use element-resize-detector's custom API to listen to resize changes:
https://github.com/d6u/resize-observer-lite/blob/master/src/index.ts#L11

unfortunately element-resize-detector is not a polyfill we could conditionally load, it's a custom API.

i believe element-resize-detector is already polluting the global namespace by creating window. elementResizeDetectorMaker. resize-observer-lite's main file could remove its dependency on element-resize-detector and fall back to window.elementResizeDetectorMaker (maybe also wrapped in a conditional to prevent errors if not included). then to prevent breaking current consumers, react-observer-lite could import element-resize-detector in a separate file which gets imported in the build step, but adds another build step which generates an alternate dist without importing element-resize-detector. react-container-query would also need to provide a second dist without the element-resize-detector dependency