Announcing the development of the next major version of the Umbraco UI Library - version 2.0 - expected to ship with Umbraco 18: https://github.com/umbraco/Umbraco.UI/discussions/1300

Is there anything for package devs to do or consider when doing a release for v18 ?

Glad you ask, I just amended the announcement with a "Umbraco CMS" paragraph: https://cdn.discordapp.com/attachments/1476848144095510579/1476873753551175690/image.png?ex=69a2b55d&is=69a163dd&hm=d4a0bea79297efe635315463767892534c4397cce2603a1b0d0ea0da0979ee23&

So if I understand then unless I use the CSS ref then I dont need to do anything in Umbraco package

> Also will the storybook at uui.umbraco.com support switching from v1 to v2 to see the visual differnces No, I'm not aware of such a feature in Storybook. However, when V2 takes over uui.umbraco.com, the dev branch for V1 will still have its own Storybook

But if I was using the components in say a Electron app or something not hosted eventually in Umbraco then I will need to do more stuff

> But if I was using the components in say a Electron app or something not hosted eventually in Umbraco then I will need to do more stuff Yeah, but that also depends. If you were already importing it through the main gateway package (uui), you don't need to do anything more than choosing one of the themes (light or dark). https://cdn.discordapp.com/attachments/1476848144095510579/1476874439931985951/image.png?ex=69a2b601&is=69a16481&hm=eacb4dd86717ffbfbc036bc364e7c49fd82539140d1c0730cd2327ec679333e7&

So only if I decided to import a single package and not the entire library

> So only if I decided to import a single package and not the entire library Yes, in that case you would probably need to do a deep-import instead, but you can also import those from the root of @Umbraco-ui/uui and your bundler should be able to tree-shake that.

Will clone later today just to preview/see what it will look like

and we are just about to replace @web/test-runner with vitest for improved speed and consolidation of configs - so it's now a pure vite library

Will we be able to use it early in v17?

Unfortunately too breaking for V17

Curious the change to light/dark mode at the UUI component level and not setting it up as CSS variables from umbraco like the current theme approach ?

What do you mean specifically? the old uui-css.css was just hardcoded "light" mode. The CMS ships with its own dark theme. We essentially just moved those variables to the UI library for anyone else to use.

OK yeh just thought odd to set dark mode on the granular UUI-components (again probably not an issue for us package devs and just advanced consumers)