Description
Describe the bug
Although #9053 claims this issue was resolved, I believe it remains unresolved.
The mentioned PR #9042 in this issue is only a solution for TS resolve in a monorepo, but the problem of accessing symlinks on Windows still persists.
For example, react-query/root.eslint.config.js is a symlink, which Windows cannot resolve, making ESLint application difficult. (In the image below, the .
is flagged as an unexpected token because Windows interprets symlinks like ../../eslint.config.js
, so the leading .
becomes an unexpected token.)
I think there are a few possible solutions:
- Officially state in CONTRIBUTING.md that tanstack-query should be developed in a Linux-based environment.
- Separate code used by sub-repositories, like eslint.config.js or files in the scripts folder, into a multi-repo structure.
- Copy the parent folder's files into each package individually (though this requires significant changes when updating parent files).
There might be other creative solutions I’m unaware of.
Since this issue remains unresolved, I’m opening a related issue.
Your minimal, reproducible example
every files on windows
Steps to reproduce
.
Expected behavior
Windows developers can work on tanstack-query without issues without running a virtual Linux environment.
Alternatively, ensure new contributors to tanstack-query are aware they need to set up a virtual Linux environment.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
Windows
Tanstack Query adapter
None
TanStack Query version
latest
TypeScript version
No response
Additional context
No response