same issue here

I guess we'll optimize it in the next major version of pnpm. I have a PR open already: #7317

However, I don't understand why you get the registry.npmmirror.com+ part in the path. Can you share your lockfile?

Thanks, it is very helpful, hope the fix 7317 can be in next major version, pnpm is excellent, but our project can not use the tool due to this problem.
For the registry.npmmirror.com+ part, I also feel weird . but now I can not reproduce it. my current version is 8.12.0
if it happen again, I will provide the lock files.

also having this issue, spent 2 days trying to figure out why our project worked fine on my mac and not on my coworkers machines. Turns out our file names are long, and pnpm makes crazy nested path lengths. Even with long file paths turned on, it would still blow up.

I find the #7317 is closed and will not be integrated to V9
May I know the reason？
When I use this solution, it can indeed solve my problem.

The issue is still not solved for all users by that fix but it makes the directories in .pnpm less readable. The solution should be to allow long paths on Windows on system level. We should try to fix it with long path prefix: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry

Also, could you just enable long paths? https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later

Thanks for advice, I remember that my collogues already try to enable the long path. but it still could not work. But I will try again.
I guess it might be relevant to one of security policy or safety software on our develop environment. Some companies have their own IT department, and they always add some security policy or safety software to develop computer.

When I change the code and set MAX_LENGTH_WITHOUT_HASH to lower value, then the problem is gone.

Maybe it could provide a choice in user side by extra parameter on the pnpm install?
User can decide to use full path or use short path.

To what value do you change MAX_LENGTH_WITHOUT_HASH?

To what value do you change MAX_LENGTH_WITHOUT_HASH?
Sorry for later reply.
If MAX_LENGTH_WITHOUT_HASH = 26 it worked
If MAX_LENGTH_WITHOUT_HASH = 60, it also worked

The bigger value, I did not have a try.
Thanks for solving

🚢 9.1.0-0

I download the 9.1.0-0 and set virtual-store-dir-max-length=80 in .npmrc
Now it works normally, Thanks!