Uncaught TypeError: Path must be a string. Received null
See original GitHub issueWhen trying to use watch functionality I get the following.
Atom Version: 1.7.3 System: Mac OS X 10.11.4 Thrown From: Remote-FTP package, v0.8.3
Stack Trace
Uncaught TypeError: Path must be a string. Received null
At path.js:8
TypeError: Path must be a string. Received null
at assertPath (path.js:8:11)
at Object.posix.resolve (path.js:426:5)
at /Users/jimmy/.atom/packages/Remote-FTP/lib/client.js:746:25
at Array.forEach (native)
at Client.module.exports.Client.watch.addListeners (/Users/jimmy/.atom/packages/Remote-FTP/lib/client.js:745:14)
at emitNone (events.js:72:20)
at Client.emit (events.js:166:7)
at ConnectorSFTP.<anonymous> (/Users/jimmy/.atom/packages/Remote-FTP/lib/client.js:283:9)
at /Users/jimmy/.atom/packages/Remote-FTP/lib/connectors/sftp.js:56:16
at SFTPStream.onReady (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/lib/client.js:758:9)
at SFTPStream.g (events.js:260:16)
at emitNone (events.js:67:13)
at SFTPStream.emit (events.js:166:7)
at SFTPStream._transform (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/node_modules/ssh2-streams/lib/sftp.js:340:14)
at SFTPStream.Transform._read (_stream_transform.js:167:10)
at SFTPStream._read (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/node_modules/ssh2-streams/lib/sftp.js:170:15)
at SFTPStream.Transform._write (_stream_transform.js:155:12)
at doWrite (_stream_writable.js:292:12)
at writeOrBuffer (_stream_writable.js:278:5)
at SFTPStream.Writable.write (_stream_writable.js:207:11)
at Channel.ondata (_stream_readable.js:528:20)
at emitOne (events.js:77:13)
at Channel.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Channel.Readable.push (_stream_readable.js:110:10)
at SSH2Stream.<anonymous> (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/lib/Channel.js:146:15)
at emitOne (events.js:77:13)
at SSH2Stream.emit (events.js:169:7)
at parsePacket (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:3163:10)
at SSH2Stream._transform (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:551:13)
at SSH2Stream.Transform._read (_stream_transform.js:167:10)
at SSH2Stream._read (/Users/jimmy/.atom/packages/Remote-FTP/node_modules/ssh2/node_modules/ssh2-streams/lib/ssh.js:212:15)
at SSH2Stream.Transform._write (_stream_transform.js:155:12)
at doWrite (_stream_writable.js:292:12)
at writeOrBuffer (_stream_writable.js:278:5)
at SSH2Stream.Writable.write (_stream_writable.js:207:11)
at Socket.ondata (_stream_readable.js:528:20)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Socket.Readable.push (_stream_readable.js:110:10)
at TCP.onread (net.js:523:20)
Issue Analytics
- State:
- Created 7 years ago
- Comments:16
Top Results From Across the Web
Nodejs: Path must be a string. Received null - Stack Overflow
I was trying to implement the following code and got the TypeError error when I ran it. app.js
Read more >"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 >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 >npm error: TypeError('Path must be a string. Received ... - Reddit
npm error: TypeError('Path must be a string. Received ' + inspect(path));\n. Node keeps ...
Read more >[Fix] TypeError [ERR_INVALID_ARG_TYPE]: The “path ...
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
I’ve created a Pull Request fixing this issue.
This should be sorted now, if anyone is having issues with this still leave a commend and I’l re open. Also if anyone has questions about the watch functionality just open another issue.