RainbowKit's CSS doesn't get bundled in production, because the way they're exposing it is with a sideEffect. Webpack's side effects are basically an infinite black hole, as denoted by this issue that's been open for 4.5 years. more context/explanation on this stack overflow answer
Details
Details
run yarn prod in landing with this diff and RainbowKit experience found on localhost/commlanding/siwe now has more than 0 styles
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- master
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
lib/webpack/shared.cjs | ||
---|---|---|
138 ↗ | (On Diff #17045) | I initially added it here. My thinking was that we're scoping the change to apply to just the case where it matters – CSS files being imported from node_modules on prod. What are the pros / cons of placing it here vs. where you placed it? |
lib/webpack/shared.cjs | ||
---|---|---|
138 ↗ | (On Diff #17045) | i moved it back there, i think scoping to where it matters makes more sense |