You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried taking a stab at this and was able to successfully upgrade the repo to React 19 and everything seems to be working alright.
Issues I faced:
The latest version of storybook 8.4.7 threw tons of errors, so I tried their latest beta version, 8.5.0-beta.5, which made a few components render.
React 18.3.1 was still being installed even after changing the version to 19.0.0 in package.json at the root node_modules. This made storybook throw tons of errors related to multiple versions of react present. Resolved it by running npm install --legacy-peer-deps as the error came from @orama/react-components not supporting 19.0.0. This install command is a bit risky though since it updated lots of other packages in package-lock.json, but overall seemed okay.
After this, storybook started complaining and wasn't compiling anymore, giving an error that it wasn't able to find react. After some investigation, realized it was looking for react at the root node_modules instead of node_modules at apps/site. Quick fix was to add react and react-dom with version 19.0.0 to root package.json which created a copy of react and react-dom in the root node modules.
I think we should hold onto the upgrade before storybook releases the version 8.5.0, and @orama/react-components updates the peer dependency for react 19 support.
as the error came from @orama/react-components not supporting 19.0.0. This install command is a bit risky though since it updated lots of other packages in package-lock.json, but overall seemed okay.
I think we should hold onto the upgrade before storybook releases the version 8.5.0, and @orama/react-components updates the peer dependency for react 19 support.
Agreed! Also, glad to see you around, @Harkunwar ❤
Activity
Harkunwar commentedon Dec 25, 2024
I tried taking a stab at this and was able to successfully upgrade the repo to React 19 and everything seems to be working alright.
Issues I faced:
8.5.0-beta.5, which made a few components render.package.jsonat the rootnode_modules. This made storybook throw tons of errors related to multiple versions of react present. Resolved it by runningnpm install --legacy-peer-depsas the error came from@orama/react-componentsnot supporting19.0.0. This install command is a bit risky though since it updated lots of other packages in package-lock.json, but overall seemed okay.node_modulesinstead of node_modules atapps/site. Quick fix was to addreactandreact-domwith version19.0.0to root package.json which created a copy ofreactandreact-domin the root node modules.I think we should hold onto the upgrade before storybook releases the version
8.5.0, and@orama/react-componentsupdates the peer dependency for react 19 support.AugustinMauroy commentedon Dec 25, 2024
Im in favour of waiting little bit. I opened an isssue on orama repo for react 19
AugustinMauroy commentedon Jan 31, 2025
News: Orama component has been updated.
I'll test something today
ovflowd commentedon Feb 1, 2025
cc @micheleriva
ovflowd commentedon Feb 1, 2025
Agreed! Also, glad to see you around, @Harkunwar ❤
AugustinMauroy commentedon Feb 1, 2025
Claudio orama side is okay !
ovflowd commentedon Mar 1, 2025
Migration completed via #7531