Taiga UI 5

[nsbarsukov]

• Update Angular to 17.x.x
• Switch all dynamic things like formatting, i18n etc from Observables to signals
• Enable built-in support for dark mode in Root with a new WritableSignal<boolean> token
• Normalize TuiPoint as [x: number, y: number] across the app and use it everywhere
• Review animations, some need more params, some are no longer used
• Review portals, maybe we can just show them all in one stack for simplicity in order of their creation
• Refactor Carousel
• Refactor Accordion
• Refactor Pagination.
  We need to break it down to 2 components, dots and number buttons.
• Refactor dialogs
  We need easier way to reuse built-in logic like closeable/dismissible for custom dialogs
• Rename @taiga-ui/icons to @taiga-ui/icons-lucide
  So that in future we can add icons-material, icons-awesome etc.
  What to do with flag icons? What to do with payment system icons?

[KhaledGabr]

Speaking of Carousel, Maybe you could consider integrating with embla-carousel .. I ended up going with it instead of using Taiga's one for my project.

https://www.embla-carousel.com/get-started/

[SkyZeroZx]

I've been reviewing the library lately and it seems great with all the addons and functionalities like aesthetics.
I'm still looking at the code but I still have a doubt if TaigaUI is completely friendly with Angular's SSR, it could be considered as an improvement since several components are going to be refactored which would make it an even better library than it already is.

[waterplea]

In v4 our entire demo portal is prerendered with all the routes — this is how we test that all our components work with SSR, this is done as a pipeline on each PR. If you see a particular issue with SSR — please report it, SSR support is important to us.