#Converting a significant number of CSS-in-JS to v7

14 messages · Page 1 of 1 (latest)

misty tartan
#

Hi, say we use createStyles, a lot, is upgrading to 7 even possible without effectively rewriting all our components?

All these files use props and pass them into styles, so I'm not even sure how we'll use the new setup without a total rewrite.

Are we confined to v6 now? Any chance of bring support back?

Thanks!

ornate jetty
#

I have the same question too, it would be really nice if there is an migration tool or script, that at least partially automate the conversion process. It is painful to re-write all those styles in css

surreal harness
#

Same here, I'm not sure we'll migrate anytime soon... that's frustrating 🤷‍♂️
it was great if there was an option to gradually migrate, to let both versions live in parallel until we migrate all

#

and there's also the styles prop to migrate 🤦‍♂️

rain jewel
#

It works for createStyles only though, styles and sx props are gone for good

misty tartan
#

This is looking quite bleak. I honestly never imagined a UI library would suddenly deprecate their central UI feature. ugh.

#

So I'm looking at options and wondering if the update is worth it, or switching to a new UI library is a better choice so we aren't stuck on 6 and only receiving bug fixes. The migration would be a pain, but I'm not upending my whole framework because of one library.

ember mist
#

migrating is not really necessary unless you have a specific reason to, like you are facing a lot of issues with SSR

plenty of us here have had apps across 4/5/6 and selectively not upgraded depending on the need

bug fixes are typically almost never a requirement for upgrade, it's just features, in my experience the library rarely has issues

misty tartan
#

Thanks for the info, our frameworks is using NextJS + Mantine and most everything is SSR involved. This may be specific to our scenario but I'm still thinking that I'm missing something. I also upgraded from earlier versions no prob, but this one is quite different in our scenario.

I think I need to think more
lumbergh

ember mist
#

this is unfortunately the reality with react now, chakra ui is having to also drop css in js, i believe mui is also scrapping it too, due to react choosing to go down the rsc route

misty tartan
#

I didn't know that, so theres a general shift

ember mist