Risto Keravuori

I hit a similar `Couldn't find a Program` error and it appears to be triggered when I add an anonymous function as a prop value to my skip-listed components (which...

@blueshw's suggestion would actually be really great, because right now styled-jsx is kind of clunky when it comes to styling third-party components without having to sprinkle `:global` the whole way...

True enough, was just pointing out the similarity in the use-cases. OP could've used `:global` in a similar way to downscale the element selectors' specificity to achieve the same outcome...

Is this something with any internal momentum? Or is it something that a community member will probably have to tackle?

This release is necessary for Node 14 support: ``` jest-enzyme > jest-environment-enzyme > jest-environment-jsdom > @jest/environment > @jest/transform > jest-haste-map > [email protected]: fsevents 1 will break on node v14+ and...

This especially effects SCSS chains in webpack, as `sass-loader`/`node-sass` defaults to the `,var` output. A workaround for this is to add `outputStyle: "expanded",` to the `sassOptions` to ensure whitespace exists...

Trying to envision what the MVP of this change would look like, so mental mapping here as I try to grok the repo. This approach avoids adding any state to...

I would argue that the debate around which comments to ignore is unnecessary. AFAICT the only reason you would ignore comments is in instances when someone has created headers/delimiters for...

@nandorojo This should be addressed by #363 and then https://github.com/software-mansion/react-native-svg/pull/1993. Together those will fix the module output of `react-native-svg` and enable proper tree-shaking. I've attached the bundle analyzer output from...