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
npx rimraf -g ./**/dist ./**/node_modules first run seems to succeed but always gives "The system cannot find the path specified." and "WARN Local package.json exists, but node_modules missing, did you mean to install?"
#304
Closed
JasonKleban opened this issue
May 1, 2024
· 5 comments
npx rimraf -g ./**/dist ./**/node_modules first run seems to succeed but always gives "The system cannot find the path specified." and "WARN Local package.json exists, but node_modules missing, did you mean to install?"
Second run doesn't emit those messages. I tried breaking that pattern into two in both orders, but no effective change.
Is it because of chains of symlinks between various nested dist & node_module folders? Is there a way to deal with this more elegantly without hurting complexity, performance, or platform agnosticism?
The text was updated successfully, but these errors were encountered:
Definitely relevant, thanks! The fact that it was succeeding anyway was throwing me off, but yeah, I do want to nuke everything. Using npx rimraf@latest -g ./**/dist ./**/node_modules@latest make sure to use the remote package instead of some random locally available one.
Ah, yes, that's another way to ensure npm runs the rimraf from an external location. Still a bit risky, since it means you have an effective dependency on *, but rimraf is about as stable a library as one could hope for, at least in the bin interface.
npx rimraf -g ./**/dist ./**/node_modules
first run seems to succeed but always gives "The system cannot find the path specified." and "WARN Local package.json exists, but node_modules missing, did you mean to install?"Second run doesn't emit those messages. I tried breaking that pattern into two in both orders, but no effective change.
Is it because of chains of symlinks between various nested dist & node_module folders? Is there a way to deal with this more elegantly without hurting complexity, performance, or platform agnosticism?
The text was updated successfully, but these errors were encountered: