Argthtjtr

I just updated the node and npm using nvm. When I start the node server I am getting this error. I tried with different solutions. This type of questions already existed in stack overflow but none of these worked for me. So I tried with these things but no use.

1.Removed node modules and install node modules with npm install.

2.Updated babel-cli version.

3.downgraded node and nvm.

4.npm i balanced-match.

5.npm i -g balanced-match.

6.npm i balanced-match --save.

I am adding my package.json

{

    "name": "******",

    "version": "1.0.0",

    "description": "",

    "main": "index.js",

    "scripts": {

         "start": "nodemon express-server.js --exec babel-node",

         "build": "babel ./ -d dist",

         "serve": "node dist/index.js"

    },

    "author": "",

    "license": "ISC",

    "dependencies": {

          "babel": "^6.23.0",

          "bluebird": "^3.5.1",

          "cookie-parser": "^1.4.3",

          "cors": "^2.8.4",

          "ejs": "^2.6.1",

          "express": "^4.16.3",

          "express-es6-template-engine": "^2.0.3",

          "express-session": "^1.15.6",

          "handlebars": "^4.0.11",

          "helmet": "^3.13.0",

          "html": "^1.0.0",

          "instamojo-nodejs": "0.0.5",

          "jsonwebtoken": "^8.2.2",

          "lodash": "^4.17.10",

          "moment": "^2.22.2",

          "mongoose": "^5.1.3",

          "mongoose-unique-validator": "^2.0.1",

          "multer": "^1.3.0",

          "mysql": "^2.15.0",

          "node-fetch": "^2.1.2",

          "node-schedule": "^1.3.0",

          "node-xlsx": "^0.12.1",

          "nodemailer": "^4.6.8",

          "passport": "^0.4.0",

          "passport-google-oauth20": "^1.0.0",

          "passport-local": "^1.0.0",

          "request": "^2.88.0",

          "request-ip": "^2.0.2",

          "sanitize-html": "^1.18.2",

          "utf8": "^3.0.0",

          "validator": "^10.2.0",

          "xlsx2json": "^1.0.0"

    },

    "devDependencies": {

         "babel-cli": "^6.26.0",

         "babel-preset-es2015": "^6.24.1",

         "babel-preset-stage-2": "^6.24.1",

         "nodemon": "^1.17.5"

    }

  }

In console it showing like this.
console error

I wasted 12 hours time to solve this problem only.

I solved this problem by installing the balanced-match with npm install balanced-match in root folder. I don't know why it is taking root folder node modules. In console error it is clearly given path but I have not aware of it. If anyone explain why it is taking root node modules that would be helpful to me.

I did not see any node packages as balanced-match. Hence, it is giving the error. You can also manually add package in package.json and run npm install.

If you ran this command: npm i balanced-match --save there would be an entry for it in your package.json file. Does your app require this module for production or is it a development tool? That will determine which flag you should pass to the install command. From the docs:

-P, --save-prod: Package will appear in your dependencies. This is the default unless -D or -O are present.

-D, --save-dev: Package will appear in your devDependencies.

-O, --save-optional: Package will appear in your optionalDependencies.

--no-save: Prevents saving to dependencies.

When using any of the above options to save dependencies to your
package.json, there are two additional, optional flags:

-E, --save-exact: Saved dependencies will be configured with an exact version rather than using npm’s default semver range operator.

-B, --save-bundle: Saved dependencies will also be added to your bundleDependencies list.

The previous answer does have the most likely fix for your problem. You can either run the install command again with the correct flag for your use case (which will install it and update your package.json), or you can add it manually and run npm install again.

When you install, are there any errors at all? If not, it should work. You can check for installed packages using npm ls (passing optional tags like '-g' will show you all globally installed modules, and you can modify the output by also passing a depth tag like such: --depth=0.