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
We have a astro based micro frontend app. We want to use tanstack query on some micro app. When i tried integrate tanstack to app its works fine until call app from host app with remote entry.
1.Create a app with vite
2.Add Module federation to app
3.Define configs for remoteEntry
4.Add Tanstack query to existing app
5.Edit config file for tanstack shared
Expected behavior
I want to use tanstack query with vite module federation
How often does this bug happen?
None
Screenshots or Videos
Platform
Browser: Brave,
OS:Windows 10
Tanstack Query adapter
react-query
TanStack Query version
5.44.0
TypeScript version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Thank you for filing this issue, but we need more information before looking into this.
Specifically, a minimal, standalone, runnable reproduction is needed - preferably with codesandbox or stackblitz. If your issue is TypeScript related, prefer a TypeScript playground.
We'll close this issue for now, but we'll certainly re-open it if there is a proper reproduction.
Describe the bug
We have a astro based micro frontend app. We want to use tanstack query on some micro app. When i tried integrate tanstack to app its works fine until call app from host app with remote entry.
MF App
vite.config.ts
Your minimal, reproducible example
Steps to reproduce
1.Create a app with vite
2.Add Module federation to app
3.Define configs for remoteEntry
4.Add Tanstack query to existing app
5.Edit config file for tanstack shared
Expected behavior
I want to use tanstack query with vite module federation
How often does this bug happen?
None
Screenshots or Videos
Platform
Browser: Brave,
OS:Windows 10
Tanstack Query adapter
react-query
TanStack Query version
5.44.0
TypeScript version
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: