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

Unable to have a root on a separate drive on Windows #8536

Closed
Robinfr opened this issue Jun 6, 2019 · 3 comments
Closed

Unable to have a root on a separate drive on Windows #8536

Robinfr opened this issue Jun 6, 2019 · 3 comments

Comments

@Robinfr
Copy link

Robinfr commented Jun 6, 2019

🐛 Bug Report

Passing a folder on a different directory on Windows to the roots configuration option fails as jest-haste-map is trying to resolve all paths relative to the rootDir, but this is not possible on Windows where a relative path from one drive to another will produce an absolute path.

This bug was introduced in #7020

To Reproduce

Steps to reproduce the behavior:

  • Have a configuration that has a root set to a different drive than the project itself is on
  • Start jest

Expected behavior

The paths that are on a separate drive should not be resolved relatively to the rootDir, but should be taken as is. We're using a patch that does this and that seems to solve the issue.

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: Windows 10
    CPU: (4) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
@github-actions
Copy link

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the Stale label Feb 17, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 30 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2023
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants