Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"TypeError: Path must be a string" after break from project

See original GitHub issue

I updated packages and all seemed fine. I took a week break from the project, ran npm install and cannot seem to figure out the cause of this error. It’s on this repo.

For convenience here is the error message and specs:

ERROR in ./src/app.js
Module build failed: TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.extname (path.js:1429:5)
    at processText (/home/kingscott/newton/node_modules/standard/node_modules/eslint/lib/cli-engine.js:144:30)
    at CLIEngine.executeOnText (/home/kingscott/newton/node_modules/standard/node_modules/eslint/lib/cli-engine.js:671:26)
    at Linter.lintText (/home/kingscott/newton/node_modules/standard-engine/index.js:65:59)
    at Object.standardLoader (/home/kingscott/newton/node_modules/standard-loader/index.js:19:12)
 @ multi app

and my packages:

"dependencies": {
    "material-ui": "^0.15.0-alpha.2",
    "react": "^15.0.2",
    "react-dom": "^15.0.2",
    "react-tap-event-plugin": "^1.0.0",
    "recompose": "^0.17.0"
  },
  "engines": {
    "node": "0.12.7"
  },
  "devDependencies": {
    "babel": "^5.8.21",
    "babel-core": "^5.8.22",
    "babel-loader": "^5.3.2",
    "standard": "^6.0.8",
    "standard-loader": "^3.0.0",
    "webpack": "^1.13.0",
    "webpack-dev-server": "^1.14.1"
  }

If you check out the repo, you can see my server.js and webpack.config.js.

Thanks.

Issue Analytics

State:
Created 7 years ago
Reactions:54
Comments:55 (10 by maintainers)

Top GitHub Comments

72reactions

PascalSenncommented, Jul 19, 2016

An upgrade to babel-core@6.10.4 may solves the problem. At least this did it im my case.

41reactions

kingscottcommented, May 10, 2016

Must be a node problem. Downgraded to node 5.11.1 and it works. Thanks for the help, you can close.

👍

Top Results From Across the Web

NODE JS - TypeError: Path must be a string. Received { request

So i install the new package and i code this from the example... app.use(async function(ctx){ await serve ...

Why do I keep getting 'path must be a string or buffer' error ...

Either your path is not actually a string (it may be a list…), or you are passing the wrong arguments to the function...

Path | Node.js v19.3.0 Documentation

A TypeError is thrown if path is not a string or if suffix is given and is not a string. path.delimiter #. Added...

dask.bytes.core - Dask documentation

This cleanly breaks data by a delimiter if given, so that block boundaries start directly ... PathLike)): raise TypeError("Path should be a string,...

body must be a string. received: undefined. - You.com | The search ...

gulp-usemin TypeError: Path must be a string. Received undefined ... I tried setting up a test project with test.pug with the following content....