Error: Socket not found. Is Chrome running with the extension?

[pandeiro]

Great idea, love the API.

I installed the unpacked extension, restarted Chrome (Mac standard install), inspected the service worker console. Seems the extension is running.

Still every surf ... command gets this error in response:

Error: Socket not found. Is Chrome running with the extension?

[tucaman]

FYI — Windows users hit this exact same error but for a different reason: the hardcoded /tmp/surf.sock path doesn't exist on Windows, and Windows doesn't support Unix domain sockets at all.

I've opened #43 for the Windows-specific root cause and #44 with a fix that uses Windows named pipes (\.\pipe\surf-sock) on win32.