Open xiongtx opened 7 years ago
Hey @xiongtx, thanks for filing this. I've been able to verify and reproduce that this is a bug.
@turbopape was the original author of this chapter so I'm not sure how to account for the bug, but what I can say is that (a) this doesn't seem to work because it doesn't actually start the websocket server, it just starts a general file server and (b) this section isn't super important in the context of the larger chapter or book (in other words, in two pages you'll get a different REPL connection technique that does work, and most of the rest of the book relies on Figwheel for a REPL instead of Weasel and Piggieback).
Please accept my apologies for the bug being there and the inconvenience :(
So you don't know how to fix it? Maybe @turbopape has a better idea?
Expected behavior
The
piggieback_project
should successfully connect to a REPL.Actual behavior
Following the instructions in the book results in a WebSocket error.
Steps to reproduce the problem
cd
to thepiggieback
projectlein repl
Backtraces if necessary (
M-x toggle-debug-on-error
)There seems to be no build-in way to save stack traces from Chrome console logs, so I did the best I could:
Environment & version information
Google Chrome:
Leiningen
Shell
OS