Ian K Smith
Ian K Smith
> One thing that this would impact is SSR rendering If `useMedia` is relying only on the props of a `` component higher in the tree (as opposed to an...
> The challenge here is during SSR we don't know which breakpoints we're rendering for so we render all the breakpoints and use media queries to control which is displayed...
I would greatly appreciate this functionality as well!
We have some internal resources planned to tackle this soon (next 2 weeks), but open to a PR if you want to see it land even sooner. Three code changes...
I've run into this problem even when my web worker does not send network requests. Removing request interception resolves the problem, though it's not ideal.
Love to see that #844 is merged! I'm very much looking forward to seeing those changes land in a published release. Any thoughts on when that might happen? As of...
> One option I'd be okay with would be to silence the warning when it's generated by modules in node_modules, since it's not actionable there anyway. Good points, I like...
> Heh - if you're running tax manually before passing things to Microbundle that would be a rollup use case. > > Any particular reason you'd need to do that...
I've encountered this issue during unit tests that depend upon `localforage`, even with the following snippet: ``` import * as localforage from 'localforage'; import * as memoryDriver from 'localforage-driver-memory'; localforage.defineDriver(memoryDriver);...
Really looking forward to seeing this merged!