Zouhir ⚡️

I like the idea of having `onScrollPassive` however, my 2cents: - the `options` object accept multiple things `{capture, passive, once}` and I don't think we should maintain a shorthand on...

Hi Ebidel, apologies for my delayed responses & inability to follow up & debug the issue yet. URLSearchParams is supported, the 2nd link has to be updated, the first link...

I never had use case where this is useful, but, when a developer explicitly calls render() I think we should do it. I will have this in mind, thanks.

I will add `force` option.

I think this is a legit use case, I will implement that.

sorry I've missed this! that's strange & interesting @farzeni @importerror ... I will be investigating closely & hopefully deploy a fix asap. fwiw, @farzeni - your fork's fix look legit

Thank you @chris480 for filing this issue, I have been thinking about writing mode and additionally the usage logical properties you suggested above. While I believe the idea is great,...

folks, I have been thinking a bit about this topic and I believe the best path forward is to actually expose 6 fold rect variables (instead of 4) representing the...

I totally don't like socket.io but I can't prioritise swapping it now as we still in beta and am really rethinking so many things

Great idea!!! 😻😻😻 But actually we don't need to do that in options. Would you consider something like: ``` // Loop through a projects npm scripts Object.keys(pkg['scripts']).forEach(K => // K...