Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vite warnings when Sourcemaps are enabled #7181

Closed
Stanzilla opened this issue Mar 26, 2024 · 1 comment
Closed

Vite warnings when Sourcemaps are enabled #7181

Stanzilla opened this issue Mar 26, 2024 · 1 comment

Comments

@Stanzilla
Copy link

Describe the bug

When sourcemaps are enabled in Vite and building for production, the following warnings are emitted:

vite v5.2.6 building for production...
node_modules/@tanstack/react-query-devtools/build/modern/index.js (1:0): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/@tanstack/react-query/build/modern/useSuspenseQuery.js (1:0): Error when using sourcemap for reporting an error: Can't resolve original location of error.
node_modules/@tanstack/react-query/build/modern/useBaseQuery.js (1:0): Error when using sourcemap for reporting an error: Can't resolve original location of error.

Your minimal, reproducible example

https://stackblitz.com/edit/vitejs-vite-6wvpyq?file=src%2FApp.css

Steps to reproduce

I tried to repro it in the stackblitz above but could not with a very basic layout, so it might just be something I do in the rest of my app. If there is any indication of that, please just close the issue.

The project is an electron react app, using Vite to bundle.

Expected behavior

No warning in console.

How often does this bug happen?

Every time

Screenshots or Videos

image

Platform

Item Value
Remote WSL: Ubuntu
OS Linux x64 5.15.150.1-microsoft-standard-WSL2
CPUs AMD Ryzen 9 3900X 12-Core Processor (24 x 3800)
Memory (System) 31.31GB (28.82GB free)
VM 0%

Tanstack Query adapter

react-query

TanStack Query version

5.28.8

TypeScript version

5.4.3

Additional context

No response

@TkDodo
Copy link
Collaborator

TkDodo commented Apr 2, 2024

yeah sorry, no idea where that warning comes from in your app, I've never seen it before. if you can't reproduce it in isolation, I won't look into it, sorry.

@TkDodo TkDodo closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants