Closed Swiftwork closed 11 months ago
Closing the issue as I didn't realize I needed to use https://github.com/heroku/heroku-buildpack-nodejs for builds on the Heroku platform. I thought this project was a successor.
@Swiftwork I'm still running into this issue while pointing to that buildpack https://github.com/heroku/heroku-buildpack-nodejs in my app.json, did you resolve how to support yarn 4 without a yarnPath?
@Swiftwork I'm still running into this issue while pointing to that buildpack https://github.com/heroku/heroku-buildpack-nodejs in my app.json, did you resolve how to support yarn 4 without a yarnPath?
We weren't able to. Just set the "yarnPath" to 4.0.1 as they have a weird check requiring the path. Not sure if it is actually used.
Our builds using
heroku/nodejs
and Yarn 4 with installs are failing to find yarnPath:Locally everything works provided
corepack enable
is run beforehand.This is the suggested [installation way by Yarn](https://yarnpkg.com/getting-started/install#per-project-install, to not include a
yarnPath
in the.yarnrc.yml
as is done in the test fixture:https://github.com/heroku/buildpacks-nodejs/blob/v2.3.0/buildpacks/nodejs-yarn/tests/fixtures/yarn-4-modules-zero/.yarnrc.yml#L3
Can you confirm that it is working on your side with a test fixture for
Yarn 4
,nodeLinker: node-modules
(non-zero),"packageManager": "yarn@4.0.0"
, and noyarnPath
?