Skip to content

deploy command with node-linker=hoisted produces empty node_modules folder #6682

@bm77525-kr

Description

@bm77525-kr

We're attempting to migrate our monorepo containing several Azure Function apps to pnpm. The main issue we're facing is the packaging/deployment of individual functions apps since Azure Functions don't support symlinks when deployed.

We've attempted to use the node-linker=hoisted option since it shouldn't create symlinks along with the deploy command, but the output of the node_modules folder ends up with just node_modules/.pnpm/lock.yaml and nothing else.

pnpm version:

8.6.2

Code to reproduce the issue:

.npmrc file

node-linker=hoisted

Command:

pnpm --filter={workspace name} --prod deploy pruned

Expected behavior:

A package is deployed from the specified workspace which contains a flat node_modules without symlinks.

Actual behavior:

The package is deployed from the specified workspace that contains a near-empty node_modules folder, containing only a single file: node_modules/.pnpm/lock.yaml

Additional information:

  • node -v prints: v16.16.0
  • Windows, macOS, or Linux?: macOS

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions