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

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.

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 54
Comments: 55 (10 by maintainers)

Commits related to this issue

fix(Path): "TypeError: Path must be a string" "TypeError: Path must be a string" after break from project Related Issue webpack/webpack#2463 — committed to PascalSenn/babel by PascalSenn 8 years ago
update babel-core to ^6.10.4 https://github.com/webpack/webpack/issues/2463#issuecomment-234670420 — committed to mygoare/react-boilerplate by mygoare 8 years ago
update for "TypeError: Path must be a string" https://github.com/webpack/webpack/issues/2463 — committed to okmttdhr/okmttdhr.github.io.src by okmttdhr 8 years ago
- fixes `”TypeError: Path must be a string" after break from project` https://github.com/webpack/webpack/issues/2463#issuecomment-247314797 - includes missing jquery as devDep - upgrades some other de... — committed to fritx/react-at by fritx 8 years ago
upgrade babel solves some strange compatibility issues, see https://github.com/webpack/webpack/issues/2463#issuecomment-233600216 — committed to hotosm/osm-analytics by tyrasd 7 years ago
- fixes `”TypeError: Path must be a string" after break from project` https://github.com/webpack/webpack/issues/2463#issuecomment-247314797 - includes missing jquery as devDep - upgrades some other de... — committed to fritx/react-at by fritx 8 years ago

Most upvoted comments

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

+72

PascalSenn on Jul 19, 2016

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

👍

+41

kingscott on May 10, 2016

I’ve seen some weird Node 6 reports so maybe that’s it?

+38

bebraw on May 10, 2016

update to babel-core@6.10.4 really help. Thank you

+34

ipostol on Jul 22, 2016

Yeah, downgraded from Node 6.2 to 5.12 and this resolved the issue for me. Thanks!!

+24

dace on Jul 9, 2016

@fyllepo It has turned into a party! 🎉

+12

kingscott on Jul 28, 2016

yup! upgrading babel-core works! Thanks everyone 😃

+12

exnie on Jul 26, 2016

Instead of downgrading node to 5.1.1 as recommended I updated babel-core to @6.10.4 and it worked pretty well!

Thank you!! 🙏🏼

+12

guicheffer on Feb 6, 2017

Downgrade node from 6.x to 5.x maybe not a good choice,because we can’t use some new feature in node 6.x then.Upgrade babel-core to the newest version can solve the problem.The newest babel-core is 6.11.4,and it works for me.

+11

smancang on Jul 26, 2016

Webpack update was the perfect solution for this issue. I’d like just to add a comment on how to update the npm packages easier. You’d need to run the following three commands in your project’s root directory:

npm i -g npm-check-updates npm-check-updates -u npm install

ehsankhf on Mar 8, 2017

I got it working now after using ncu (npm-check-updates) to fetch the latest versions:

react-redux          ^5.0.5  →  ^5.0.6
eslint-plugin-react  ^7.1.0  →  ^7.2.0
webpack              ^3.5.1  →  ^3.5.2
webpack-dev-server   ^2.7.0  →  ^2.7.1

Node: v8.2.1 NPM: 5.3.0

Pie4kaiz on Aug 10, 2017

i meet the same question

➜  ~ node -v
v8.1.0
➜  ~ npm -v
5.0.4

the error message

ERROR in ./app/index.js
Module build failed: TypeError: Path must be a string. Received undefined

and i update my babel-core version to 6.11.4, it`s work well @yorkie Great! It helps me.

ruoru on Jun 27, 2017

For anyone who hasn’t upgraded NPM recently, use npm install -g npm per @bolivar’s suggestion.

bpartridge on Feb 28, 2017

Upgrading npm solved my problem but thanks a lot guys!!!

bolivar on Jan 25, 2017

This issue is resolve in https://github.com/taobaofed/react-web/issues/136 :

use node 5.x instead of node 6

add a key 'publicPath' to the webpack config output node

output:{
    publicPath:''
}

flyskywhy on Nov 25, 2016

Just joining the party… and celebration for babel-core to @6.10.4 – Glad I googled this as I was about to start debugging!

fyllepo on Jul 28, 2016

Had to downgrade to node v5.12 and babel-core is at v6.25.

Annoying that I can’t even use the LTS version of Node.

greygatch on Jul 27, 2017

I had the same issue for node v6.8.0: I solved the Problem by updating to:

    "babel-core": "6.17.0",
    "html-webpack-plugin": "2.16.0",

dreampulse on Oct 14, 2016

You might need to update update html-webpack-plugin as well.

princed on Sep 15, 2016

Upgrading babel-core to 6.11.4 seems to fix this issue with node6, why this still gets opened?

yorkie on Aug 18, 2016

Same issues here, looking forward to see it merged!

mirague on Jul 14, 2016