Dom Armstrong

You can map the import in jest config https://github.com/styled-components/styled-components/issues/4081

Another related issue https://github.com/styled-components/styled-components/issues/4073. I've not seen any feedback regarding this issue yet but seems like a major breaking bug since v6 (and stopping us from being able to upgrade...

I've had a further dig in to this and it appears to be because when running in Jest the `dist/styled-components.cjs.js` is used, and when built with webpack the `./dist/styled-components.browser.esm.js` (or...

Another similar reproduction https://codesandbox.io/s/styled-components-6-regression-gr2732?file=/src/App.js. There seems to be a regression using `&`. The main styled component class is used to replace `&` but since the stylesheets don't get removed, once...

Looks like this is now fixed as of 6.1.5 🥳 https://codesandbox.io/s/styled-components-6-regression-forked-2rwf29

Changing yarn to not use pnp is not really a solution. The command should use yarn not npm if the package manager for the project is yarn.

I've found there is actually quite an easy fix for this. Add a build command to your package.json and prefix it with yarn. package.json ``` `"build-stories": "yarn build-storybook ..."` ```...

I've removed this package from our dependencies now, it doesn't seem like it's adding too much, the only rule that mattered to us was `'no-empty-source': null,` so I added that...

I've created an alternative PR which shouldn't require any external api change https://github.com/isaacs/node-lru-cache/pull/378

It appears that any time a lazy component is initialised it also kicks in the 300ms suspense, even if there is nothing that needs to load. We have our bundle...