You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well windows and \ are no fried and I hate PowerShell for it with a passion.
Anyway, this command unexpectedly added a \ as a package, which seemed to create a link to a local package at the root directory.
After trying to revert that by fixing the package.json and a pnpm installs, I received errors in the project.
I tried a clean reinstall with deleted node_modules where, subsequently, pnpm installed the pnpm store on the E: drive (the lost drive where the project was located) instead of the correct path E:\.pnpm-store\.
This should have been a warning sign that something went wrong with pnpm configuration when it thinks E: is the new root.
Without knowing what happened I decided to reset pnpm. I manually deleted the files that pnpm had placed incorrectly in E: and then ran a pnpm store prune.
However, since pnpm mistakenly thought its store root was E:, it ended up wiping everything on that drive.
This is only my assumption, as it was the latest stuff I did on the drive.. And the package I was working in mystically survived while everything else got wiped of the face of the earth.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I encountered an issue in a project where I installed a package using the following command under Windows PowerShell
Well windows and
\
are no fried and I hate PowerShell for it with a passion.Anyway, this command unexpectedly added a
\
as a package, which seemed to create a link to a local package at the root directory.After trying to revert that by fixing the package.json and a pnpm installs, I received errors in the project.
I tried a clean reinstall with deleted node_modules where, subsequently,
pnpm
installed the pnpm store on the E: drive (the lost drive where the project was located) instead of the correct pathE:\.pnpm-store\
.This should have been a warning sign that something went wrong with
pnpm
configuration when it thinksE:
is the new root.Without knowing what happened I decided to reset
pnpm
. I manually deleted the files thatpnpm
had placed incorrectly in E: and then ran apnpm store prune
.However, since
pnpm
mistakenly thought its store root was E:, it ended up wiping everything on that drive.This is only my assumption, as it was the latest stuff I did on the drive.. And the package I was working in mystically survived while everything else got wiped of the face of the earth.
Beta Was this translation helpful? Give feedback.
All reactions