A panic when failing to connect to the socket about godet HOT 2 CLOSED

well, the problem is the missing error check on godet.Connect (that in case of error returns remote = nil)

While I could be checking the value of the receiver, should I do that in every call ? I don't think I have ever seen any code where object methods check the value of the receiver in order to avoid an error.

But I will update the example to check the error code for godet.Connect.

Regarding to the root cause (not being able to connect to Chrome), try godet/cmd/godet/main.go.
In there I have some code that starts the browser with the correct options (should work on MacOS and Linux, and if your browser is installed in a non standard location you can specify an alternative command to run)

from godet.

I agree that a check in every call is not necessary, and your README changes make sense and encourage proper error checking. So thanks!

from godet.