Open joscha opened 7 years ago
@joscha How/Where to do use the plugin atm? Did you see postcss-icss-composes
? :) In case you didn't the logic was split into its own plugin, but the logic there changed aswell, the plugin itself is syntax only, resolving/fetching
needs to be done by the middleware, that's WIP as I currently undertand and I don't do to 💯 atm myself 😛
@michael-ciniawsky I see - are there any docs on how to upgrade from postcss-modules-values@1.x
to postcss-icss-values@2
& postcss-icss-composes@2
? I added both postcss-icss-values
and postcss-icss-composes
now instead of the old module, but it doesn't seem to work as expected.
I'm currently writing docs, but they are WIP atm and a few points are still WIP in general, use the lastest postcss-modules-*
in 'production' etc. for now, they all got an final upgrade to work with PostCSS 6 before the rename. ICSS is a complete shift under the hood in terms of plugin logic and there are no 'runners/resolvers' atm to test them out in a project
Will do, ta!
After updating from
postcss-modules-values@1.3.0
topostcss-icss-values@2.0.1
I get the following errors in my CSS build:The CSS files look like this:
ui/shadows/shadows.cs
:and the one using it,
badge.stories.css
:any idea what could have caused this in the upgrade?