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

Empty resolutions after turbo prune #1842

Closed
oceandrama opened this issue Sep 2, 2022 · 3 comments
Closed

Empty resolutions after turbo prune #1842

oceandrama opened this issue Sep 2, 2022 · 3 comments
Assignees
Labels
area: windows Issues specifically reproducing on Windows kind: bug Something isn't working

Comments

@oceandrama
Copy link

What version of Turborepo are you using?

1.4.3

What package manager are you using / does the bug impact?

Yarn v2/v3 (node_modules linker only)

What operating system are you using?

Windows

Describe the Bug

After turbo prune in out folder yarn.lock has empty resolution field in all dependencies:

"@adobe/css-tools@npm:^4.0.1":
  version: 4.0.1
  resolved: ""
  integrity: ""

And after yarn install it generates the following error:

Assertion failed: Expected the lockfile entry to have a resolution field (@adobe/css-tools@npm:^4.0.1)

Expected Behavior

yarn install works correctly

To Reproduce

In the basic example:

  1. yarn set version latest
  2. yarn config set nodeLinker node-modules
  3. yarn install
  4. yarn turbo prune --scope=web
  5. copy out folder somewhere (to exclude it from monorepo)
    In the out folder:
  6. yarn set version latest
  7. yarn config set nodeLinker node-modules
  8. yarn install
@chris-olszewski
Copy link
Contributor

Yarn 2+ is currently in a broken state when it comes to prune. See #643 and the linked issues for more details.

@chris-olszewski chris-olszewski added the kind: bug Something isn't working label Sep 2, 2022
@oceandrama
Copy link
Author

@chris-olszewski Thanks for quick response! I will keep a close eye on it

@mehulkar mehulkar added the area: windows Issues specifically reproducing on Windows label Sep 8, 2022
@chris-olszewski
Copy link
Contributor

With #2019 and the release of 1.5 this should be fixed. Please update and reopen if the issue persists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: windows Issues specifically reproducing on Windows kind: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants