You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
pnpx @turbo/codemod update
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
pnpm why turbo
Describe the Bug
Expected Behavior
The expected outcome for running pnpx @turbo/codemod update should be:
Successful execution of the @turbo/codemod update command, applying necessary updates to bring the codebase in line with Turborepo version 2.2.3.
Proper installation of the latest version of turbo as a dev dependency.
No workspace-related or version mismatch errors if all dependencies are correctly specified.
To Reproduce
To reproduce this issue, you would need a similar setup:
Use PNPM in a monorepo environment with workspaces.
Have a dependency (@metajob/next-local) defined in one of the packages with a workspace: version (e.g., @metajob/next-local@workspace:^0.0.1).
Attempt to add or update turbo in a nested directory instead of at the root of the monorepo.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Verify canary release
Link to code that reproduces this issue
pnpx @turbo/codemod update
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
pnpm why turbo
Describe the Bug
Expected Behavior
The expected outcome for running pnpx @turbo/codemod update should be:
Successful execution of the @turbo/codemod update command, applying necessary updates to bring the codebase in line with Turborepo version 2.2.3.
Proper installation of the latest version of turbo as a dev dependency.
No workspace-related or version mismatch errors if all dependencies are correctly specified.
To Reproduce
To reproduce this issue, you would need a similar setup:
Use PNPM in a monorepo environment with workspaces.
Have a dependency (@metajob/next-local) defined in one of the packages with a workspace: version (e.g., @metajob/next-local@workspace:^0.0.1).
Attempt to add or update turbo in a nested directory instead of at the root of the monorepo.
Additional context
No response
The text was updated successfully, but these errors were encountered: