Windows with its file-in-use semantics has this behaviour:
$ npm install npm@latest -g
npm ERR! code EEXIST
npm ERR! path C:\Program Files\nodejs\npm
npm ERR! EEXIST: file already exists
npm ERR! File exists: C:\Program Files\nodejs\npm
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\robertc\AppData\Local\npm-cache\_logs\2021-05-03T21_24_41_721Z-debug.log
which is not rust-wasm's problem to fix, but it is rust-wasm's problem if the book suggests running the command, or depends on the command having been run successfully.
Where in the docs did you come across this?
Describe what about it does not make sense
Windows with its file-in-use semantics has this behaviour:
which is not rust-wasm's problem to fix, but it is rust-wasm's problem if the book suggests running the command, or depends on the command having been run successfully.
Why does it not make sense?
How could we improve it?