You're on Windows, but trying to run a script designed for linux (it has linux path separators, which confuse Windows).

Inside an npm script, you can refer to locally installed package binaries by name. Doing so will eliminate your path issue.

    "test": "export NODE_ENV=test && mocha --timeout 100000",
    "prestart": "sequelize db:migrate  && sequelize db:seed:all",
    "start": "pm2 start pm2server.config.js",
    "poststart": "pm2 log HumanR"

You might also run into an issue with the export NODE_ENV=test command. You'll need cross-env for that.

npm install --save-dev cross-env

Then in package.json:

    "test": "cross-env NODE_ENV=test mocha --timeout 100000",

If your make executable is in C:/Program Files (x86)/GnuWin32/bin, add it to your path.

The purpose of "add path" is for convenience for your later use.

Assume your make executable is located in C:/Program Files (x86)/GnuWin32/bin/make.

Before you add the path you need to call:

C:/Program Files (x86)/GnuWin32/bin/make

After you add the path you need to call:

make

If you are familiar with programming in Linux, I highly recommend msys2.

It provide a package manager pacman that you can easily update your tool chain and libraries. (g++, make, cmake, etc)