Skip to content

fix: link global not working#9515

Closed
btea wants to merge 4 commits intopnpm:mainfrom
btea:fix/link-global-invalid
Closed

fix: link global not working#9515
btea wants to merge 4 commits intopnpm:mainfrom
btea:fix/link-global-invalid

Conversation

@btea
Copy link
Copy Markdown
Member

@btea btea commented May 11, 2025

close #9506

@btea btea requested a review from zkochan as a code owner May 11, 2025 04:11
@btea btea marked this pull request as draft May 11, 2025 04:22
@btea btea marked this pull request as ready for review May 11, 2025 07:31
Comment on lines +115 to +118
// https://github.com/orgs/pnpm/discussions/9037
// The pnpm-workspace.yaml file may only contain other configurations without the packages field.
const workspaceManifest = await readWorkspaceManifest(opts.workspaceDir)
if (!workspaceManifest?.packages && (params == null || params.length === 0)) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it shouldn't matter if it is a multi-package workspace or single-package one. It should always work the same and link to global.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

pnpm-workspace.yaml make pnpm link not working

2 participants