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

Asking for the root of the repo to migrate #9386

Open
1 task done
praneetscgb opened this issue Nov 5, 2024 · 0 comments
Open
1 task done

Asking for the root of the repo to migrate #9386

praneetscgb opened this issue Nov 5, 2024 · 0 comments
Labels
kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage

Comments

@praneetscgb
Copy link

Verify canary release

  • 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

IMG-20241105-WA0003

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

@praneetscgb praneetscgb added kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage
Projects
None yet
Development

No branches or pull requests

1 participant