Open maxshay opened 5 months ago
@maxshay Could you solve it? I have the same problem
@cmanuelpriver not really solved, but the first time i ran it, it seems like the migrations part was all successful. So i manually updated the turbo version from "^1.13.3" to "^2.0.4" in the package json, and did a pnpm install
. And it seems to run fine.
If that doesn't work for you just create a separate turborepo app using the lastest version using the cmd line. And make sure the turbo related files look the same. Shouldn't be a lot of files for a regular project.
I solved, I had problems with nvm and windows, I deleted everything and tried again and it worked, I never knew what the specific problem was.
@maxshay Thank you for your help
same problem here..
I was facing the same issue. It seems the migration is expecting a dotEnv
property in tasks.build in turbo.json. I added that, and it completed successfully.
{
"$schema": "https://turbo.build/schema.json",
"globalDependencies": ["**/.env.*local"],
"tasks": {
"build": {
"env": [],
"dotEnv": [".env", ".env.local"] // <-- add this
}
// ...
Verify canary release
Link to code that reproduces this issue
na
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
na
Describe the Bug
While upgrading turborepo with
npx @turbo/codemod@latest update
I ran into the following error:Error message:
Expected Behavior
Does not error and completes the migration successfully after running a second time.
To Reproduce
Migrating turbo repo from
1.13.3
to latest withnpx @turbo/codemod@latest update
. I was also updating eslint versions and some internal packages' (eslint config and typescript config) names and didn't replace all references in my apps that referenced them. Not ideal but it happened this way. Runningnpx @turbo/codemod@latest update
the first time resulted in what seemed like a successfull migration:Until it got to the last part there of upgrading turbo with pnpm. And since package references were wrong pnpm failed, thus migration failed.
I fixed the references, ran pnpm install in the root to make sure, and reran
npx @turbo/codemod@latest update
and got the error noted in Describe the BugSince the migrations succeed the first time I manually updated the package.json turbo version to
"^2.0.3"
and pnpm installed. And everything seemed to work ok.A rare edge case but still reporting nonetheless.
Additional context