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

kingscott · 2016-05-10T00:48:55Z

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.

The text was updated successfully, but these errors were encountered:

bebraw · 2016-05-10T03:44:59Z

Could you try upgrading to standard 7? Feels like a standard related bug to me.

kingscott · 2016-05-10T03:54:30Z

The error persists. I've swapped out some of my code (new build processes for old etc), updated/downgraded packages. And not sure what it is.

bebraw · 2016-05-10T03:57:34Z

Ok. The next step would be digging into ESLint. Maybe logging near the offending line would give better insight. It might stem from standard-loader configuration somehow so that's another place to inspect.

kingscott · 2016-05-10T04:31:24Z

Hmm, we'd have to dig into ESLint even if I'm not explicitly using ESLint?

bebraw · 2016-05-10T05:34:45Z

See processText at the trace.

bebraw · 2016-05-10T05:58:11Z

What command do I have to run to repro? I tried a few, no luck. I see

ERROR in ./src/app.js
Module not found: Error: Cannot resolve 'file' or 'directory' ../backgrounds.js in ../king/src
 @ ./src/app.js 25:21-49

though.

kingscott · 2016-05-10T13:31:07Z

I can include that file. I excluded it from source control and would prefer to have it not on GitHub. I can email you the file, and then you would just checkout the nasa-update branch and run:

➜  ~  npm install
➜  ~  npm start

bebraw · 2016-05-10T13:37:25Z

Works for me.

king [nasa-update] $ npm start

> [email protected] start .../king
> NODE_ENV=development node server.js

Listening at localhost:2020
Hash: 22dd0f5206c2641317ba
Version: webpack 1.13.0
Time: 3776ms
             Asset     Size  Chunks             Chunk Names
    ./lib/build.js   980 kB       0  [emitted]  app
./lib/build.js.map  1.15 MB       0  [emitted]  app
chunk    {0} ./lib/build.js, ./lib/build.js.map (app) 924 kB [rendered]

WARNING in ./src/app.js
<text>:22:8: Closing curly brace does not appear on the same line as the subsequent block.
webpack: bundle is now VALID.

Maybe I'm missing something. Running on OS X so that could be it. There's some difference.

kingscott · 2016-05-10T13:40:35Z

If you navigate to localhost:2020 what do you get?

bebraw · 2016-05-10T13:40:57Z

It shows some photo background and time(?) then.

kingscott · 2016-05-10T13:44:40Z

Hmm weird. I was getting the same error on OS X as well as Linux.

bebraw · 2016-05-10T13:47:26Z

It's really hard for me to say anything concrete. You would have to look at the stack trace and go from there. Perhaps someone else can repro.

In any case, this might fit Stack Overflow better as it seems the issue is somewhere else than webpack core.

kingscott · 2016-05-10T13:49:22Z

I am slightly confused as to why you cannot replicate the bug, what version of node and npm are you running?

bebraw · 2016-05-10T13:51:01Z

king [nasa-update] $ node -v
v5.10.1
king [nasa-update] $ npm -v
3.8.3

bebraw · 2016-05-10T13:51:36Z

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

kingscott · 2016-05-10T13:53:58Z

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

👍

bebraw · 2016-05-10T13:55:20Z

Ok. You could consider reporting this upstream to standard-loader.

kingscott · 2016-05-10T13:55:44Z

I'll give it a shot, thanks @bebraw.

felix-d · 2016-05-15T18:57:35Z

Had the same issue and no stack trace to help me debug this whatsoever. Downgraded from node 6 to 5 and... success! Thanks!

wiiiim · 2016-05-15T22:14:58Z

same here 👍

kingscott · 2016-05-15T22:26:22Z

Hey @felix-d @wiiiim, this helped me in the end!

Cheers!

JohnnyMa · 2016-06-04T07:11:43Z

Great! It helps me to resolve the same issue. Thanks! 👍

jkomyno · 2016-06-08T21:15:07Z

Thank you guys!

yarhtut · 2016-06-26T01:04:03Z

Thanks you guys

dace · 2016-07-09T06:21:42Z

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

jcubic · 2016-10-20T08:12:52Z

@binarious did you try to update node-sass or sass-loader?

binarious · 2016-10-20T08:14:35Z

@jcubic both are at their latest versions.

binarious · 2016-10-20T08:36:13Z

Seems to be a bug somewhere else: webpack-contrib/sass-loader#285

ximet · 2016-11-05T09:39:28Z

I have the same problem. Env: node.js version: 7, "webpack": "1.13.3", "babel-loader": "6.2.7", "react-hot-loader": "1.3.0", "babel-core": "6.18.2". Other loader is missing.

flyskywhy · 2016-11-25T01:58:27Z

This issue is resolve in taofed/react-web#136 :

use node 5.x instead of node 6

or

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

output:{
    publicPath:''
}

webpack/webpack#2463 (comment) - includes missing jquery as devDep - upgrades some other deps - improves README

solves some strange compatibility issues, see webpack/webpack#2463 (comment)

bolivar · 2017-01-25T14:50:09Z

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

bpartridge · 2017-02-28T20:39:45Z

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

ehsankhf · 2017-03-08T08:49:58Z

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

ruoru · 2017-06-27T07:06:38Z

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.

29er · 2017-07-11T03:11:03Z

I had to downgrade to node 6.11 ( I was on 8 ) and upgrade to babel-core to 6.11.4 and it worked.
doing one or the other did NOT work. FYI

greygatch · 2017-07-27T16:56:05Z

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.

Pie4kaiz · 2017-08-10T08:31:36Z

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

webpack/webpack#2463 (comment) - includes missing jquery as devDep - upgrades some other deps - improves README

pkerpedjiev · 2018-09-05T18:03:31Z

I get this error using:

NPM: 5.6.0
NODE: 9.9.0
webpack-dev-server: 2.6.1

It disappears if I remove the devtool: 'cheap-source-map' option from my webpack.config.js.

bebraw added the bug label May 10, 2016

bebraw closed this as completed May 10, 2016

kingscott mentioned this issue May 10, 2016

"TypeError: Path must be a string" after break from project standard/standard-loader#64

Closed

bebraw reopened this May 24, 2016

bebraw added the node6 label May 28, 2016

andreme mentioned this issue Nov 1, 2016

update babel wdjungst/react-project#56

Closed

gabro mentioned this issue Nov 4, 2016

Node 6 support buildo/react-components#655

Closed

sota1235 mentioned this issue Nov 5, 2016

node.js v6~対応する sota1235/hubot-reviewer-choice#15

Open

BradlySharpe mentioned this issue Nov 9, 2016

ERROR in ./assets/js/core.js Module build failed: TypeError: Path must be a string. Received undefined MozaikAgency/wp-theme-starter#268

Open

MrBlenny mentioned this issue Nov 13, 2016

path.dirname(undefined) bug in v0.12.1 getsentry/raven-node#233

Closed

fritx added a commit to fritx/react-at that referenced this issue Dec 14, 2016

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

9be4e55

webpack/webpack#2463 (comment) - includes missing jquery as devDep - upgrades some other deps - improves README

stevage mentioned this issue Dec 15, 2016

CLI inline presets not working? babel/babelify#221

Closed

jdollar mentioned this issue Jan 7, 2017

Fixing issues with babel core on a fresh install and addressing batch test failures goatslacker/alt#706

Open

tyrasd added a commit to hotosm/osm-analytics that referenced this issue Jan 8, 2017

upgrade babel

991218b

solves some strange compatibility issues, see webpack/webpack#2463 (comment)

jessedobbelaere mentioned this issue Feb 13, 2017

Upgrade babel-core choffmeister/Paw-JsonWebTokenDynamicValue#5

Open

markerikson mentioned this issue Mar 2, 2017

Beginner question. markerikson/react-redux-cesium-testing-demo#5

Closed

samussiah mentioned this issue Mar 22, 2017

Fix log axis and update builds. RhoInc/Webcharts#40

Merged

mlunoe mentioned this issue Apr 26, 2017

Upgrade node to 8 and npm to 5.0.3 dcos/dcos-ui#2136

Closed

kriss145 mentioned this issue Jun 3, 2017

Update babel-core dependency Pagepro/libsasserplate#8

Merged

bwindsor mentioned this issue Sep 7, 2017

Add Czech language and Start to dictionary template Maprunner/cd#11

Merged

fritx added a commit to fritx/react-at that referenced this issue Nov 6, 2017

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

c7d3caa

webpack/webpack#2463 (comment) - includes missing jquery as devDep - upgrades some other deps - improves README

IT0315 mentioned this issue Mar 30, 2018

"Path must be a string. Received undefined" zkat/npx#144

Closed

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

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

Comments

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

bebraw commented May 10, 2016

kingscott commented May 10, 2016

felix-d commented May 15, 2016

wiiiim commented May 15, 2016

kingscott commented May 15, 2016

JohnnyMa commented Jun 4, 2016

jkomyno commented Jun 8, 2016

yarhtut commented Jun 26, 2016

dace commented Jul 9, 2016

jcubic commented Oct 20, 2016

binarious commented Oct 20, 2016

binarious commented Oct 20, 2016

ximet commented Nov 5, 2016 • edited Loading

flyskywhy commented Nov 25, 2016

bolivar commented Jan 25, 2017

bpartridge commented Feb 28, 2017

ehsankhf commented Mar 8, 2017

ruoru commented Jun 27, 2017

29er commented Jul 11, 2017 • edited Loading

greygatch commented Jul 27, 2017

Pie4kaiz commented Aug 10, 2017

pkerpedjiev commented Sep 5, 2018

ximet commented Nov 5, 2016 •

edited

Loading

29er commented Jul 11, 2017 •

edited

Loading