Skip to content

[Windows] symlink doesn't work yet #9272

Open
@ss0526100

Description

@ss0526100

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.)

Image

I think there are a few possible solutions:

  1. Officially state in CONTRIBUTING.md that tanstack-query should be developed in a Linux-based environment.
  2. Separate code used by sub-repositories, like eslint.config.js or files in the scripts folder, into a multi-repo structure.
  3. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions