[test] Only build component packages for codesandbox #17976
Conversation
|
No bundle size changes comparing 79fad65...c62a957 |
|
@CompuIves I expected codesandbox to still appear in the checks section. It is installed (according to GitHub UI): |
|
@eps1lon Should we try to uninstall/install? |
Sounds like a good idea 👍 |
|
uninstalled |
|
installed back |
|
It doesn't seem to work. |
57a1c7a to
f1b7217
Compare
|
Hm we could make this work for our packages by patching the version in the package.json. I'll figure something out. |
4d18b7d to
3c41ec1
Compare
|
@CompuIves Using the same version doesn't work since codesandbox thinks the version string points to a package on the npm registry. https://codesandbox.io/s/create-react-app-52hbg |
3c41ec1 to
c62a957
Compare
|
For now we have a codesandbox for the most common use case I imagine (testing components). For styles we need to wait for resolutions. But this is already a great first step. |

Without
resolutionsbuildingstyleswould be pointless/corewould still list the latest stable as its dependency.