@tanstack/react-query version
I am building on open-saas template built with Wasp version 0.16.0. The version is now 0.16.3. Wasp requires @tanstack/react-query "^4.29.0". It doesn't matter how many time "npm install" is invoked after adding "^4.29.0" to the package.json. I found out that the version "4.29.0" no longer exist in npm, and that "4.29.5" is the latest in the series. Now, the issue is every time npm install is invoked version 4.39.1 is always on the tree. I need you assistance in resolving this.
22 Replies
Hi @CharlesO. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information in the knowledge sources, Wasp currently dictates the exact versions of certain dependencies it uses internally, including @tanstack/react-query. If you try to specify a different version in your package.json, Wasp will report a conflict and refuse to build. This is by design: you must use the version that Wasp specifies, and you cannot override it with a different version, even if the version Wasp requires is no longer available on npm. This can lead to issues if a required version is unpublished or otherwise unavailable, as you are experiencing. Wasp's dependency resolution currently uses simple string comparison and does not semantically resolve overlapping version ranges, which can also cause false positives for version conflicts Project Dependencies Docs Dependency Version Checking Issue.
Your situation—where Wasp requires @tanstack/react-query "^4.29.0", but that version is no longer available on npm, and npm installs a newer version instead—highlights a limitation in Wasp's current dependency management. There is no documented workaround in the knowledge sources for forcing npm to install an unavailable version, nor is there a way to tell Wasp to accept a newer compatible version.
What you can do:
- You may want to follow or comment on the relevant Wasp GitHub issues, such as Allow specifying npm dependency that Wasp already uses, with different version and Dependency Version Checking, as this is a known limitation and is being discussed by the Wasp team.
- There is no official solution or workaround documented in the knowledge sources for this problem at this time.
Summary:
Wasp currently requires you to use the exact version of @tanstack/react-query it specifies, and there is no supported way to override this or resolve the issue if that version is no longer available on npm. This is a known limitation, and the Wasp team is aware of it, but there is no documented fix or workaround yet. If you need to proceed urgently, you may need to wait for an update from the Wasp team or consider using a different template or version of Wasp that specifies a version of @tanstack/react-query that is available on npm. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @CharlesO, 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?
Wasp currently requires you to use the exact version of @tanstack/react-query it specifies, and there is no supported way to override this or resolve the issue if that version is no longer available on npm. This is a known limitation, and the Wasp team is aware of it, but there is no documented fix or workaround yet. If you need to proceed urgently, you may need to wait for an update from the Wasp team or consider using a different template or version of Wasp that specifies a version of @tanstack/react-query that is available on npm. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @CharlesO, 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?
This issue is resolved by upgrading to Wasp 0.16.5
It shouldn't be an issue anyway, if latest version with fix is 4.39.1, it should be installed with ^4.29.0 match
I wonder if version check jsut didn't care about minor/patch applied and wanted exact version
Hey @CharlesO, the guys are correct. Are you still experiencing problems?
No longer after upgrading to 0.16.5, which even the VS Code Copilot is unaware of. Thanks, sidic.
Has Wasp 0.16.5 been tested with Node.js 22?
Our minimum node version is 20, but I do everything with 22 locally and it works.
Btw if you want access to rest of the server you should drop a message in #👋introductions .
Help! I am working with the Opensaas template with Wasp version: "0.16.5". Which @sendgrid version works with this wasp version best. I can login with Google, but not with email-and-password. Another issue, I can sign up several times with one email with no error. Thanks for your assistance.
@CharlesO Hey, if you use wasp's emailsender functionality, which supports sendgrid, it should set it up for you automatically.
We don't automatically connect accounts if the same email is used.
e.g. if someone registers with
email-and-password with email franjo@wasp.sh, and then uses Google register with franjo@wasp.sh google account, those will be 2 separate accounts. They are not connected. This is for security reasons.
Also if you try to register with already used email adress, we always pretend like you successfully registered even if the account already exists. This is again for security reasons. So malicious actors can't guess if somebody already registered with a given email address.
But when you have new issues it's best to open up a new thread in #🙋questions, so we can index the questions better.
Also it allows the kapa.ai to solve them (sometimes).Thanks, franjo.
Wohooo @CharlesO, you just became a Waspeteer level 1!
@kapa.ai , is there anyway to fix this issue with react-query that doesn't require upgrading WASP? I'm on version 0.14 and really don't want to upgrade if I can help it. I'm close to launching my product and don't want to derail with any surprises.
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry, but based on the knowledge sources, there is no documented way to resolve the @tanstack/react-query version issue in Wasp without upgrading Wasp itself. Wasp enforces strict dependency versions for packages it uses internally, and if the required version is no longer available on npm, there is no supported workaround or override mechanism. This limitation is acknowledged by the Wasp team and is being discussed in open issues, but no fix or alternative approach is provided for users who cannot or do not want to upgrade Wasp at this time Allow specifying npm dependency that Wasp already uses, with different version Dependency Version Checking.
If you are close to launching and want to avoid surprises, the safest path according to current knowledge is to either upgrade Wasp (which you wish to avoid) or wait for an official fix from the Wasp team. There is no documented workaround for your situation in the provided sources.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @JLegendz, 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?
@kapa.ai , my mistake. I'm on version 13 still.
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the knowledge sources, there is no documented way to resolve the @tanstack/react-query version issue in Wasp 0.13 without upgrading Wasp. Wasp enforces strict version requirements for internal dependencies like @tanstack/react-query, and if the required version is no longer available on npm, you cannot override or bypass this restriction. This limitation is acknowledged in the Wasp documentation and related GitHub issues, and there is currently no supported workaround for users who cannot upgrade Wasp Project Dependencies Docs Allow specifying npm dependency that Wasp already uses, with different version.
If you are close to launching and want to avoid surprises, the only options according to the knowledge sources are to upgrade Wasp (which you prefer not to do) or wait for an official fix from the Wasp team. Unfortunately, there is no alternative solution documented for your situation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @JLegendz, 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?
@JLegendz , there is nothing you have to do really with react-query issue. The problem was caused by their broken release, but they made a new release, so now it should all be fine.
If you are having issues on the Wasp side with react-query, that is almost certianly caused by that broken react-query version being cached on your side, be it dev setup or on your production server, in the
node_modules. Best best is to do wasp clean, delete node_modules, and maybe even package-lock.json -> after that, Wasp should pull in the latest react-query version, which is not broken, and all is good. This is all regardless of your Wasp version.
Let us know if you will have specific issues here, with error messages and as much context/info as possible and we will be happy to try to assist, although it should come down to what I wrote above.I went ahead and updated everything to version 0.16, I was able to deploy fine from there. Thank you though!
is there any new news on account linking? 😃😇👀
For now no. I wouldn’t count on it being implemented soon.
@A³Learn so we plan to publish the Wasp Dev Roadmap on the next LW, which will be happening in ~2 weeks, and that Roadmap will contain Auth epic, and that epic contains account merging/linking. Focus of Dev Roadmap will be on what needs to be done by 1.0, and will be capturing ~20-30 epics.
Auth epic will be one of the more important ones, and likely one that will be worked on sooner than most others. And while the main focus in Auth epic will be refactoring Auth so that adding new providers is much easier, both for us and for users, and also redesigning the API so it is nicer and better layered, one of the next things after that is account merging/linking.
TLDR: In 2 weeks we will public Roadmap with account linking on it, and while not top priority, it is one of the important tasks on it. What does that mean timewise? Can't say yet, depends on in which order we attack stuff on the Roadmap, but I would say by the end of the year it might happen.
Stay tuned!
we having a 1.0 launch party too?
He he we will once it's out 😄