Question: When will @itwin/tree-widget-react version 4 move out of alpha to a stable release?

[arome]

Question

The @itwin/tree-widget-react package version 4.x (currently 4.0.0-alpha.27) is still marked as alpha. Is there a timeline for when version 4 will reach a stable, production-ready release?

We are currently using version 4 in production in our app which is why we would like some clarity on the roadmap.
Are there any known blockers or major features still under development for version 4 that affect the timing? Any insight into the current progress would be greatly appreciated.

[grigasp]

Hi @arome.

The only blocker for this package to leave alpha is dependency on @stratakit packages. This package relies on a number of UI components from those packages and we can't have a stable release until one of our primary peer-dependencies is stable. The latest recommendation for us is to switch to StrataKit/MUI for UI components, but:

1. The StrataKit/MUI library at this point is also unstable, AFAIK.
2. The MUI library doesn't have a Tree component that tree-widget package needs. I heard some thoughts that maybe StrataKit team will migrate the existing Tree to MUI, but I believe nothing has been done to make that happen.
3. We have consumers that are against us moving to MUI any time soon (mostly due to reason number 1 above, also the cost of migrating to MUI for them, also a number of other reasons).

As a result, we need to at least wait for 1-2 to be resolved. Then, we can start working on 3.

Tagging @iTwin/stratakit team for visibility & openness.

[GerardasB]

1. Since MUI components are used directly, usage of MUI should be stable. Most work is planned around tokens and internals before stabilizing the version numbers Stabilizing foundations stratakit#1346
   Although, it makes sense to wait for upgrade to MUI v9 stratakit#1400 to be released
2. We are planning to keep the Tree component from @stratakit/structures package. Revive structures stratakit#1355

[grigasp]

thanks, @GerardasB

Since MUI components are used directly, usage of MUI should be stable.

While the components themselves are stable, what I had in mind is styling that comes from @stratakit/mui. I guess that falls into the tokens bucket.