npm is warning me about version conflicts in @forge/react@10.1.0, which seems to depend on Atlaskit.
I’m a newbie with both Forge and NPM. Is it true that Atlaskit’s dependency on react"^16.8.0" means that I have to use that version of React in Forge? I’m confused about that because the Forge app examples all seem to depend on react"^18.2.0".
Could you help me understand the conflict? I’d really appreciate it. Thanks.
Atlaskit has been stuck on React 16 for a while, however it usually works with React 18 as long as you run npm install --legacy-peer-deps to ignore that warning, after the first time you’ll get a package-lock.json that will keep track of which specific versions you have installed and you shouldn’t see that error anymore.
It’s not amazing, but it is what it is 
Thank you very much @PaoloCampanelli. It is a huge relief to me that there is a sensible way forward. I really appreciate you taking the time to respond.
Hi @PaoloCampanelli , is it possible to use Tailwind css in Custom UI because I tried using it in my app and it did not reflect the changes in the UI, am I missing something in the manifest file?
As long as you’re correctly loading Tailwind’s CSS in your <head>, I don’t see any reason why it wouldn’t work. If you’re having issues I’d suggest you create a new thread with all the relevant details
