Open nickrttn opened 4 months ago
Hi, in turbo 2.0, we changed the environment variable mode to be strict instead of loose by default. This means that environment variables are not passed to the tasks. This could be the source of your issue. Could you try adding ENABLE_EXPERIMENTAL_COREPACK
to your environment variable config in either env
or globalEnv
? Alternatively, you could try running in loose mode by passing --env-mode=loose
in your turbo command.
Could you try adding ENABLE_EXPERIMENTAL_COREPACK to your environment variable config in either env or globalEnv?
I just attempted this, but that didn't help.
Alternatively, you could try running in loose mode by passing --env-mode=loose in your turbo command.
This did help and builds are now completing. Are there any resources about going from --env-mode=loose
to strict env mode?
Hi, in turbo 2.0, we changed the environment variable mode to be strict instead of loose by default. This means that environment variables are not passed to the tasks. This could be the source of your issue. Could you try adding
ENABLE_EXPERIMENTAL_COREPACK
to your environment variable config in eitherenv
orglobalEnv
? Alternatively, you could try running in loose mode by passing--env-mode=loose
in your turbo command.
I encountered the same situation, but now I encountered:
No more than 12 Serverless Functions can be added to a Deployment on the Hobby plan. Create a team (Pro plan) to deploy more.
I'm not trying to be cheap, but I left software 2 years ago to write a couple papers related to my background in physics, and this app is the thing that's hopefully going to make me un-homeless now that they're both in peer review.
It is a rather large framework that I actually tried to reach out to part of the Vercel team about potentially partnering on because it aligns so closely with your platform and the path Vercel seems to be on, but I wasn't having this issue before this most recent update which involved almost 2 days of just trying to get things to build on Vercel due to different versioning issues that came out of nowhere.
The app I'm running on Vercel wouldn't be the actual framework itself, although the framework would allow user's to publish their own notes and research (potentially on Vercel) once the app is released in the next couple weeks, but just a documentation and configuration site. I can't imagine that there's significantly more going on with this app than most hobby level apps.
I'm all in on sending you guys $20 a month as soon as this app gets some users and a couple sponsors or supporters, but my bank account has had the same $0.24 in it for the past month or two.
Also... I'd still love to partner on the framework if your team is interested, it can bring an entirely new demographic to Vercel in students and academics that don't write web apps themselves, but most of all I just need the documentation site to build!
Verify canary release
Link to code that reproduces this issue
https://github.com/nickrttn/eexist-repro
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?
2.0.4
Describe the Bug
On Vercel, with the following conditions:
turbo@2.x.x
ENABLE_EXPERIMENTAL_COREPACK
set to1
"packageManager": "pnpm@9.4.0+sha256.b6fd0bfda555e7e584ad7e56b30c68b01d5a04f9ee93989f4b93ca8473c49c74",
in the rootpackage.json
(as set bycorepack
)Vercel will throw an error during package installation with the following log:
Expected Behavior
To install all packages without errors.
To Reproduce
Deploy the shared reproduction to Vercel
Additional context
This workflow used to work in
turbo@1.x.x
. We use it because we include branches of an open-source repository in a closed-source repository for testing and internal usage purposes, while also wanting to keep the OSS repo public for other implementers of our package.