Path must be a string. Received undefined
See original GitHub issueI got the following error when trying to run the suggested code on grunt.
Running "babel:dist" (babel) task
Warning: Path must be a string. Received undefined Use --force to continue.
Any help?
Issue Analytics
- State:
- Created 8 years ago
- Comments:8
Top Results From Across the Web
"Path must be a string. Received undefined" #144 - zkat/npx
npm v5.51 node v8.9.0 ... it seems that anytime I run an npx command it shows "Path must be a string. Received undefined"...
Read more >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 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 >Error: Path must be a string. Received undefined - Forge
In my case const { WebClient } = require("@slack/web-api"); was causing the problem. Changing it to import declaration didn't fix the issue ...
Read more >the "path" argument must be of type string or an instance of url ...
Have you run into the error “TypeError [ERR_INVALID_ARG_TYPE]: The “path” argument must be of type string. Received undefined”? In this story I'll go...
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 FreeTop 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
Top GitHub Comments
For what its worth I was having this issue and updated all packages according to this thread https://github.com/webpack/webpack/issues/2463 and it ended up being the html-webpack-plugin not having a filename property. Hope that helps someone!
The problem for me ended up being an incorrect path to my source file. The error message was just super ambiguous.