-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: no longer crash for single projects with global dependencies (#5002
) ### Description Fixes #4914, this is the pnpm implementation of #4240 Was caused as `pnpm` when calculating ignores touches the file system and will error if `pnpm-workspace.yaml` isn't present. This also avoids failing on the rare case of someone using turbo on a single project with no external dependencies as pnpm won't create a lockfile in this case. ### Testing Instructions Added integration test for a single project using pnpm with global dependencies --------- Co-authored-by: Chris Olszewski <Chris Olszewski>
- Loading branch information
1 parent
f886022
commit ef9f6b8
Showing
3 changed files
with
15 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6 changes: 6 additions & 0 deletions
6
turborepo-tests/integration/tests/single_package/dry-run-pnpm.t
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
Setup | ||
$ . ${TESTDIR}/../../../helpers/setup.sh | ||
$ . ${TESTDIR}/../_helpers/setup_monorepo.sh $(pwd) single_package pnpm@8.0.0 | ||
|
||
We only care about this running sucessfully and not the json output | ||
$ ${TURBO} run build --dry=json > /dev/null |