React Router Dependency Issue
Getting an error: Error: Dependency conflict for user dependency (react-router-dom, ^6.23.1): Version must be set to the exactly the same version as the one wasp is using: ^5.3.3
Is Wasp on V5? If so, are there plans to update?
4 Replies
Hi @Sam Jakshtis. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Yes, based on the information provided, it appears that Wasp is currently using version
^5.3.3 of react-router-dom. This is why you're seeing an error when trying to use a different version (^6.23.1). In the current version of Wasp, if Wasp is already internally using a certain dependency with a certain version specified, you are not allowed to define that same npm dependency yourself while specifying a different version. If you do that, you will get an error message telling you which exact version you have to use for that dependency source (https://wasp-lang.dev/docs/project/dependencies).
However, there is an open issue on the Wasp GitHub repository to allow specifying an npm dependency that Wasp already uses, with a different version. The implementation of this feature would allow a user to specify any version they like, and this should be implemented internally via npm aliases source (https://github.com/wasp-lang/wasp/issues/59).
As for updating react-router-dom to version 6, there was a closed issue suggesting to update to React 18 and other libraries once they are widely adopted, and react-router-dom version 6 was one of the libraries mentioned. However, it's not clear from the provided sources when or if this update will happen source (https://github.com/wasp-lang/wasp/issues/723).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Sam Jakshtis, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?It was a public holiday today and most of the team was off, we'll get back to you tomorrow 🙂
@Sam Jakshtis yeah still on v5, we delayed updating of some bigger deps for a bit because we are working on some bigger breaking-change features at the moment (external prisma, TS SDK/DSL, full stack modules, ...) but we will soon be taking moment to update all the packages, especially the router and prisma.
@martinsos Thank you for the update!