Issue with React 17 support

[rebeccaalpert]

From Andy Pickering:

I'm hitting warnings when running npm install due to the React version. I'm using React 17 and can't upgrade because I'm developing a web console plugin. The Chatbot depends on framer-motion and react-markdown versions that both require React 18+

Maybe those package versions need to be downgraded in the Chatbot to something that supports React 17?

Or maybe I'm just missing something? I can suppress the warnings by adding "react": "17.0.2" and "react-dom": "17.0.2" to overrides , but I guess that's not the best solution?

We are on "react-markdown": "9.0.1", and "framer-motion": "11.3.28".

It looks like react-markdown 8.0.7 and framer-motion 6.5.1 supported 17. A third-party contributed that particular piece of the extension originally and we haven't touched it. We should try downgrading so we can support 17 the way we say we do.

[rebeccaalpert]

Would potentially lose support for 19 from React-Markdown if we downgrade: remarkjs/react-markdown#879. Types also get busted - would require some rewriting.

Framer is an easy drop-in replacement, but may cause support issues for 18 and 19. I would rather drop framer and custom-roll our own moving div.

[rebeccaalpert]

Talked to the PF team and we will drop framer, but recommend using the override for react-markdown for now as long as it works. React-markdown is pretty central to the way the Message component functions. I will update documentation/peer deps in a separate PR tied to this ticket.

[rebeccaalpert]

Used old version of PF React Seed with 17 to pull in latest ChatBot pre-release and was able to run it, with some type and import changes. Markdown parser seemed to work with overrides to React 17. Just going through and checking components to make sure they still work.