You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
yarn why postcss-modules-scope
yarn why v1.18.0
[1/4] 🤔 Why do we have the module "postcss-modules-scope"...?
[2/4] 🚚 Initialising dependency graph...
[3/4] 🔍 Finding dependency...
[4/4] 🚡 Calculating file sizes...
=> Found "[email protected]"
info Reasons this module exists
- "_project_#@utilitycss#atomic#postcss-modules#css-modules-loader-core" depends on it
- Hoisted from "_project_#@utilitycss#atomic#postcss-modules#css-modules-loader-core#postcss-modules-scope"
- Hoisted from "_project_#@dx#dev-ui#gatsby#css-loader#postcss-modules-scope"
info Disk size without dependencies: "816KB"
info Disk size with unique dependencies: "1.84MB"
info Disk size with transitive dependencies: "5.24MB"
info Number of shared dependencies: 18
The text was updated successfully, but these errors were encountered:
Hello,
on consumer side of this package we run into issues with not synced post-css versions.
Not sure if that update could fix usage of electrons inside multiple css selctors. But can we give it a try ?
The text was updated successfully, but these errors were encountered: