In my monorepo project, I have workspaces A and B. Workspace A depends on B being built first, with each workspace in its own folder as defined in pnpm-workspace.yaml
packages:
- 'src/mydepa'
- 'src/mydepb'
{
"name": "@mydep/a",
"scripts": {
"build": "standard build script"
}
}
{
"name": "@mydep/b",
"scripts": {
"build": "standard build script"
},
"dependencies: {
"@mydep/a": "link:../mydepb
}
}
I'm struggling to figure out how to instruct pnpm to build A before B (and C and D). When using standard npm, the order of workspace packages determines the build execution. I remove the workspaces entry from the root package.json before running pnpm.
"workspaces": [
"src/mydepa",
"src/mydepb",
],
Even after trying different methods like:
pnpm run --recursive --workspace-concurrency=1 --aggregate-output --report-summary build
I found that pnpm continues to build out of order.
{
"executionStatus": {
"/path/to/mydepb": {
"status": "failure",
"duration": 1804.710345,
"error": {
"code": "ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL",
"errno": 2,
"pkgid": "@mydep/b@",
"stage": "build",
"script": "standard build script",
"pkgname": "@mydep/b",
"prefix": "/path/to/mydepb"
},
"message": "@mydep/b@ build: `standard build script`\nExit status 2",
"prefix": "/path/to/mydepb"
},
"/path/to/mydepa": {
"status": "queued"
}
}
}
The monorepo builds correctly when done manually or with npm workspaces due to the folder order in the workspaces array.
Attempts like using --reverse=true or --resume-from=@mydep/a didn't impact the executionStatus at all.