`Path must be a string` error on `verb readme`
See original GitHub issue> verb readme
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)
at Object.dirname (path.js:1324:5)
at Liftoff.run (/Users/Vaughan/nvm/versions/node/v6.0.0/lib/node_modules/verb-cli/bin/verb.js:133:27)
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
TypeError: Path must be a string. Received null; at index.js:116:15 ...
Try reinstalling verbose/verb#dev and verb-generate-readme . This issue on generate is probably referring to the same problem you're having. We updated the ...
Read more >Gulp error: Path must be a string - laravel - Stack Overflow
The problem is that the options have been moved from the third to the fourth parameter. You can run it with: mix.sass('app.scss', null, ......
Read more >README - Sinatra
Error handlers run within the same context as routes and before filters, which means you get all the goodies it has to offer,...
Read more >Paths and Operations - Swagger
In Swagger terms, paths are endpoints (resources) that your API exposes, such as /users or ... Query string parameters must not be included...
Read more >chromium / external / github.com / juju / errors - Google Git
Errorf creates a new annotated error and records the location that the error is created. This should be a drop in replacement for...
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
I’m finding it difficult to debug…lots of magic going on.
base-runner/node_modules/log-utils
ansi-colors
etc.
closing based on lack of response. I suggest reading the node.js documentation to learn how “the magic” of modules and debugging work.