Upgrade Storybook manager to React 18

[shilman]

Is your feature request related to a problem? Please describe

Storybook's own "manager UI" is currently using React 16, which is not the latest.

Describe the solution you'd like

We should upgrade to React 18 and do the minimum to get the UI working again.

Note that this means that addons "manager entries" will also run in React 18, so it's a breaking change that will affect our addon ecosystem.

After the upgrade we should re-enable React strict mode, reversing #20345

Also, when upgrading we should upgrade the addon API to support the most recent React 18 hooks, as described in #21034

Describe alternatives you've considered

No response

Are you able to assist to bring the feature to reality?

no

Additional context

No response

[thebuilder]

You should be able to revert #20345 when #20368 is merged.

[eddilou]

It would also be nice to update all dependencies.

[dohooo]

Oh, Can not wait more. 🤯

[shogohida]

Hi @shilman can I work on this?

[shilman]

@shogohida That would be amazing! 🙏 Please check out how to contribute in our docs and feel free to ask questions in #contributing in our Discord.

[shogohida]

@shilman
Thanks for your comment! I will need some help since this is the first issue of Storybook for me to deal with. I will ask questions in Discord when I need help

[macck7]

is issuse still open...
I am new here and want to work on first issuse..

[shogohida]

Hi @macck7, I'm still working on this issue even though it's taking time 🙏

[iamkelv]

hi, @shilman , I think if the React version is to be upgraded t Ract 18 then some of the packages may also need an update else react18 may not be compatible with some older packages.

or if the issue is only focused on Upgrade then I will like to work on it.

[BradMcGonigle]

Related to #21034, is there a known workaround for using new React 18 hooks like useId in components (which we have stories for)?

I understand not being able to use the new hooks in addons but should this prevent something like useId from being used in our React 18 compatible component library?

[agriffis]

I understand not being able to use the new hooks in addons but should this prevent something like useId from being used in our React 18 compatible component library?

This shouldn't be a problem. (I do it all the time.) I suggest opening a separate issue if it's not working for you.

[vanessayuenn]

Closed by #24514