TypeError: Path must be a string. Received undefined
See original GitHub issueFollowing up on https://github.com/browserify/resolve/issues/177#issuecomment-453364771 (not sure whether it’s related), 1.9.0
has this code:
which throws an error if fs.realpath
fails and the error is ENOENT
, because then realStart
is not defined.
TypeError: Path must be a string. Received undefined
This was already fixed in master in a commit prior to the release 1.9.0
(https://github.com/browserify/resolve/commit/2321cd4b4e184f9c97f76ea50dd49b9e42927b93#diff-688ede0ee2da1fa3d89f2fc485f39273), however has not yet been released.
Here is the same part with the fix on master:
Can we get this fix out any time soon?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 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 >Meteor 1.5.2 TypeError: Path must be a string. Received ...
Meteor 1.5.2 TypeError: Path must be a string. Received undefined ... When I do meteor build and deploy to server, I get this...
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
Please see https://github.com/browserify/resolve/compare/v1.9.0...simonhaenisch:fix-path-must-be-string, here is the test results without and with the fix.
Before:
After:
(ran with Node v8.15.0 on macOS)
My branch is based of
v1.9.0
, but I’m not sure how to open a PR against that because it seems I can only open one against a branch but not a tag. Maybe you’ll have togit checkout -b v1.9.0-patch v1.9.0
first and push it, so I can open the PR?I don’t have a Windows instance to run the tests on btw.
Merged into the next v1 release (will be v1.10.0); not yet merged into master. When it is, this will close.