TypeError: Path must be a string. Received undefined
See original GitHub issueWhen using Webpack 2.
See the original issue for the explanation and my workaround: https://github.com/jtangelder/sass-loader/issues/298
path.js:7
throw new TypeError('Path must be a string. Received ' + inspect(path));
^
TypeError: Path must be a string. Received undefined
at assertPath (path.js:7:11)
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Jest TypeError: Path must be a string. Received undefined
I solved this issue using: npm uninstall -g jest; npm install -g jest; npm cache clean; npm install.
Read more >"Path must be a string. Received undefined" #144 - zkat/npx
Happy to try to help. The reason people all over www get 'Path must be a string' in Windows is because it it...
Read more >path must be a string. received undefined when building a ...
I'm attempting to build a xamarin.ios project on a hosted agent. The project builds fine on a private agent we use, but in...
Read more >Path must be a string. Received undefined - node-steam-user
Stack Trace: TypeError: Path must be a string. Received undefined at assertPath (path.js:28:11) at Object.join (path.js:489:7) at userData ...
Read more >TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument ...
After saving the file getting Error: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type undefined ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, I won’t provide a sample repo but other people coming from google can. This issue is not just mine though, you can see at least 2 other people in the linked issue having the same error.
Fell free to reopen issue if your problem not solved.