New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pnpm i in workspace throws a type error in pnpm.cjs as it can't read property 'manifest' of undefined on windows #4904
Comments
Is this fixed? |
Well, it was not yet published. |
I am getting the same error. What's the solution for this. |
I just had a similar error and it was a bear to debug. I ended up adding some console output to the 'getAllProjects' function in pnpm.cjs to see what was going wrong. Turns out that my CMD custom startup command sets the CWD to "c:\blah..." whereas the code in getAllProjects has a dictionary that tries to resolve stuff to "C:\blah...". Make sure your CWD starts with upper-case C: |
I meet the same error, solved temporarily by running cmd in vscode |
Same error in v8.4.0. Using cmd does not resolve. |
Done one more fix in this PR: #6525 |
pnpm version:
I've switched between multiple versions and they all cause this, so it makes me think the culprit is something else and that pnpm workspaces don't work well on windows machines.
Code to reproduce the issue:
Actual behavior:
Additional information:
node -v
prints:node v: 16.15.1
npm v: 8.12.2
pnpm version: 7.3.0
I have just now manually cleaned up all my app data, node, npm, pnpm, roaming data, program files as well as environment variables, did a reboot and installed everything from scratch.
Error persists.
The error occurs in this recursive function which I copied from the line of code mentioned in the error:
If I on-the-spot-dirty change that to use safe null accessing, the next error is thrown about the manifest:
non verbose second error:
that manifest assignemnt it's trying to assign the manifest property of an object that does not exist, throwing that type error, my guess is the manifestsByPath[prefix] isn't resolved properly for windows paths?
Not sure where to look in the source code fo this though.
The text was updated successfully, but these errors were encountered: