Jason Quense
Jason Quense
I will add that I've use/used astroturf in a number of high stakes production apps, and can attest that it's a solid choice, even if it's not a fan favorite....
it does do that, i've had to do `{ '__DEV__': true }` to trick it...
It might be that it just messes with the scope/binding info enough that it doesn't connect them anymore. Or maybe it tracks through the callExpression, not the callee? Seems like...
That is correct. No TS types for this but it has got a really simple interface
is tree-shaking going to _do_ anything in React's case, given that everything is preprocessed into a single flat bundle? I wonder what the primary import style is for React, personally...
So for some context the issue that brought me here was shorthand properties breaking a site of ours. I think it's fine to not have a full on browserlist integration,...
if you are on the v1 code line you can change the various popper.js config options to handle these cases.
Cards aren't a general "feed" component so that pattern i don't think is appropriate for any and all cards. Cards are simply presentation wrappers around sections and content, they aren't...
I don't disagree with anything your saying, my point is more that picking a specific keyboard navigation style would be limiting Card use-cases in a way that doesn't make sense...
Idk I'm not sure it's worth the minor convenience to using classes directly. The problem is really that it balloons the component API significantly which is problematic for `as` accepting...