Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
kingscott opened this issue May 10, 2016 · 9 comments
Closed

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

kingscott opened this issue May 10, 2016 · 9 comments

Comments

@kingscott
Copy link

Encountered this issue, and resolved it by downgrading node to v5.11.1 from v6.0.0.

Took a week break from a project, then cloned, and did the regular steps but got this error:

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

Turns out downgrading node was the solution. This is the branch I am using.

Thanks.

@kingscott
Copy link
Author

kingscott commented May 11, 2016

Although the problem still persists with node v6.0.0, standard v7.0.1 and standard-loader v3.0.1.

@ghinda
Copy link

ghinda commented May 12, 2016

@kingscott Can you try installing from my fork? The standard upgrade to 7.0.1 fixes it for me on node 6.1.0.

npm install https://github.com/ghinda/standard-loader.git#fix-string-path

@kingscott
Copy link
Author

kingscott commented May 12, 2016

Seems to be an error trying to install that URL. It works for me in browser. But npm cannot seem to find it.

EDIT: I had the wrong version of node selected. It does work, thanks! Just curious, what did you edit?

👍

@ghinda
Copy link

ghinda commented May 13, 2016

@kingscott Just updated standard to 7.0.1. Here's the PR changeset:

https://github.com/timoxley/standard-loader/pull/65/files

@kingscott
Copy link
Author

I was able to install standard 7.0.1 and all is good.

Thanks! @ghinda! 💯

@timoxley
Copy link
Contributor

@kingscott I just released standard-loader 4.0.0 which allows container app to specify which version of standard to use, please update and let me know if this works for you.

@kingscott
Copy link
Author

@timoxley It's working for me!

@bookercodes
Copy link

You're awesome. Thank you for writing this in easy-to-search words.

@alex-shamshurin
Copy link

@alexbooker Yes, it helped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants