'rm' is not recognized as an internal or external command

Hi! Context:

• I know nothing of node.js (like, the first time I copied the line of command, I kept the “<” around the address for the config file, This is my very first time using node.js)
• I’m on Windows

EDIT: I’ve understand (I think) a bit more and I think I’ve mostly disrupted things by using npm and npx. So, after I’ve deleted everything. I’ve tried these new steps:

• took the config file from the readme and adjusted it (put the right path, chose my options and deleted the template line)
• ran Node.js command prompt
• Ran

npx -p yarle-evernote-to-md@latest yarle --configFile config.json

And I still get that one and only message: “The system cannot find the path specified.” 😕 I’m probably missing something but can’t understand what.

I’ve tried copying the default template in a default-template.ts file and link that in the config file, but it doesn’t work either.

Old version

Steps I’ve taken:

• downloaded the latest release (3.12.4d) and unzipped it
• completed the config file with my infos
• installed Node.js
• Run the node.js command prompt
• cd “path to the unzipped yarle folder”
• npm i (got errors and warnings)
• npm run build (got errors)
• npx -p yarle-evernote-to-md@latest yarle --configFile /config.json (got a message “The system cannot find the path specified”)

I’ve run that last one multiple times with different config parameters and with an absolute path to config, but I always get the same message)

When I run “npm i”, here’s what I get:

> execSync@1.0.2 install C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\execSync
> node install.js

[execsync v1.0.2] Attempting to compile native extensions.
Error: spawn node-gyp ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:465:16)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn node-gyp',
  path: 'node-gyp',
  spawnargs: [ 'rebuild' ]
}
[execSync v1.0.2]
    Native code compile failed!!
    Will try to use win32 extension.

> utimes@4.0.3 install C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\utimes
> node-pre-gyp install --fallback-to-build && node-gyp clean

node-pre-gyp WARN Using request for node-pre-gyp https download
[utimes] Success: "C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\utimes\lib\binding\Release\node-v83-win32-x64\utimes.node" is installed via remote

C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\utimes>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" clean )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" clean )

> fast-xml-parser@3.12.5 postinstall C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\fast-xml-parser
> node tasks/postinstall.js

              Donating to an open source project is more affordable

                  *** Thank you for using fast-xml-parser! ***

                 Please consider donating to our open collective
                      to help us maintain this package.

                https://opencollective.com/fast-xml-parser/donate
                                      or
                   https://www.patreon.com/bePatron?u=9531404
                                      or
   https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KQJAX48SPUKNC

                                     ***



> nodemon@2.0.5 postinstall C:\Users\cuill\Downloads\yarle-3.12.4d\node_modules\nodemon
> node bin/postinstall || exit 0

Love nodemon? You can now support the project via the open collective:
 > https://opencollective.com/nodemon/donate

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.1 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 541 packages from 1219 contributors and audited 545 packages in 18.216s

18 packages are looking for funding
  run `npm fund` for details

found 4 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

and when I run “npm run build”, I get this:

> yarle-evernote-to-md@3.12.4-d build C:\Users\cuill\Downloads\yarle-3.12.4d
> npm run clean && npm i  && tsc --project ./src/tsconfig.json


> yarle-evernote-to-md@3.12.4-d clean C:\Users\cuill\Downloads\yarle-3.12.4d
> rm -f -r ./out && rm -f -r ./dist && rm -r -f ./node_modules

'rm' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! yarle-evernote-to-md@3.12.4-d clean: `rm -f -r ./out && rm -f -r ./dist && rm -r -f ./node_modules`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the yarle-evernote-to-md@3.12.4-d clean script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\cuill\AppData\Roaming\npm-cache\_logs\2021-03-25T15_22_18_801Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! yarle-evernote-to-md@3.12.4-d build: `npm run clean && npm i  && tsc --project ./src/tsconfig.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the yarle-evernote-to-md@3.12.4-d build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\cuill\AppData\Roaming\npm-cache\_logs\2021-03-25T15_22_18_839Z-debug.log

You’ll find attached the two logs mentioned here. 2021-03-25T15_22_18_839Z-debug.log 2021-03-25T15_22_18_801Z-debug.log

Does anyone know what I’m missing for this to work? Have I done something wrong in the config file? (I couldn’t find all the same parameters that are described in the readme and found some there that are not described but I don’t think this should change much…)