Last pnpm version that worked

Oct 13, 2025 by recoveryshake.com 130 views

Introduction

pnpm is a popular package manager for JavaScript projects, known for its speed and efficiency. However, with the release of version 10.6.x, some users have reported issues with the dlx command, specifically when attempting to read the project manifest. In this article, we will delve into the details of this issue, explore the possible causes, and provide a solution to get back to working with pnpm.

Last pnpm version that worked

The last version of pnpm that worked without issues was 10.5.2. This version did not exhibit the problem of attempting to read the project manifest when using the dlx command.

pnpm version

The version of pnpm that is currently experiencing the issue is 10.6.1. This version is the latest available at the time of writing, and it is the one that is causing problems with the dlx command.

Code to reproduce the issue

To reproduce the issue, you can run the following command:

pnpm --allow-build=core-js --package=hello-world-npm dlx hello-world-npm

This command attempts to use the dlx command with the --allow-build option, which is where the issue arises.

Expected behavior

The expected behavior when running the above command is that it should output "Hello World NPM". However, this is not what happens.

Actual behavior

When running the above command, you will receive the following error:

ERR_INVALID_ARG_TYPE The "path" argument must be of type string. Received undefined

pnpm [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined at Object.join (node:path:1268:7) at tryReadProjectManifest (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:13211:45) at readProjectManifest (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:13199:29) at createProjectManifestWriter (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:134112:96) at Object.handler (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:188972:106) at Object.handler [as dlx] (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:210803:50) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async /home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:221052:23 at async main (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:221010:34) at async runPnpm (/home/csauve/.local/share/mise/installs/pnpm/10.6.1/dist/pnpm.cjs:221277:5)

Additional information

It appears that pnpm is attempting to read the project manifest when using the dlx command, but only when using the allow-build option. This is a new behavior that was introduced in version 10.6.x, and it is causing problems for some users.

Node.js version

The Node.js version being used is 22.14.0.

Operating System

The operating system being used is Linux.

Solution

To resolve this issue, you can try the following:

Downgrade to pnpm 10.5.2: If you are experiencing this issue, you can try downgrading to pnpm 10.5.2, which is the last version that worked without issues.
Use a different version of pnpm: If downgrading is not an option, you can try using a different version of pnpm, such as 10.6.0 or 10.5.1.
Report the issue: If none of the above solutions work, you can report the issue to the pnpm team, and they may be able to provide a fix or a workaround.

Conclusion

Q: What is the issue with pnpm 10.6.x?

A: The issue with pnpm 10.6.x is that it attempts to read the project manifest when using the dlx command, but only when using the allow-build option. This is causing problems for some users.

Q: What is the expected behavior of the `dlx` command?

A: The expected behavior of the dlx command is that it should output the result of the command, without attempting to read the project manifest.

Q: What is the actual behavior of the `dlx` command in pnpm 10.6.x?

A: The actual behavior of the dlx command in pnpm 10.6.x is that it attempts to read the project manifest, resulting in an error.

Q: What is the error message that is displayed?

A: The error message that is displayed is:

ERR_INVALID_ARG_TYPE The "path" argument must be of type string. Received undefined

pnpm [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined

Q: What is the cause of the issue?

A: The cause of the issue is that pnpm 10.6.x is attempting to read the project manifest when using the dlx command, but only when using the allow-build option.

Q: How can I resolve the issue?

A: To resolve the issue, you can try the following:

Downgrade to pnpm 10.5.2: If you are experiencing this issue, you can try downgrading to pnpm 10.5.2, which is the last version that worked without issues.
Use a different version of pnpm: If downgrading is not an option, you can try using a different version of pnpm, such as 10.6.0 or 10.5.1.
Report the issue: If none of the above solutions work, you can report the issue to the pnpm team, and they may be able to provide a fix or a workaround.

Q: What is the impact of this issue?

A: The impact of this issue is that it prevents users from using the dlx command with the allow-build option, which can be a problem for users who rely on this feature.

Q: Is this issue specific to a particular operating system or Node.js version?

A: No, this issue is not specific to a particular operating system or Node.js version. It has been reported by users on multiple operating systems and Node.js versions.

Q: Can I use a workaround to resolve the issue?

A: Yes, you can use a workaround to resolve the issue. One possible workaround is to use a different version of pnpm, such as 10.6.0 or 10.5.1.

Q: How can I stay up-to-date with the latest information on this issue?

A: You can stay up-to-date with the latest information on this issue by following the pnpm team on social media or by checking the pnpm GitHub repository for updates.