This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
Builds for public project that use yarn 2 (or above) with workspaces are failing #762
Labels
type: bug
code to address defects in shipped code
Is your build failing?
Our builds our failing. We use
yarn 3.2.0
with workspaces in a public repo.This is the step where yarn fails:
Describe the bug
A bit of context: in yarn 1.x only private repos can have workspaces, but this limitation was removed in yarn 2:
The problem is in the
run-build-functions.sh
file:As you can see it tries to output information about the workspaces with yarn 1.x. in the command substitution and redirects STDERR to
/dev/null
. After that it only checks if the process exited with 0 or an error code, but ignores the error message, which would tell us, that 'workspaces can only be enabled in private projects'. Here's an example for the problem from the theatre-js/theatre repo:To Reproduce
Steps to reproduce the behavior:
https://github.com/theatre-js/theatre
Configuration
Right now we use the UI to configure our deploy previews, but I can give you the values we set there:
Expected behavior
In an ideal situation the workspaces should be detected, cached and restored when possible.
Build Output
Link to the logs: https://app.netlify.com/sites/theatrejs-playground/deploys/623de90057211c0008613a1a#L75
Full logs
Additional context
The text was updated successfully, but these errors were encountered: