-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REPL Window] undefined namespace when starting a shadow-cljs cljs REPL Window #115
Comments
This is fixed in version 2.0.49. |
This was not fixed in version 2.0.49! The root cause for the problem is that the cljs repl is connected but no application is connected. In this situation the code:
The returned promise contains literally nothing and the resulting I tested this issue with the calva cljs-lib - and I have no idea how to "connect an application to the REPL" for that project. |
You press F5 😄 It's mentioned here: https://github.com/BetterThanTomorrow/calva/wiki/How-to-Contribute |
It is not much we can do about ”no prompt when no app”, but we could, maybe, detect the situation. I have tried many times, and failed. That is not to say it is not possible. I had a chat with Thomas Heller about this some months ago, and he mentioned a message bus that shadow-cljs has, that could probably be used to make Calva know what state the connection is in. |
That's a problem: you cannot run the debug instance in the directory you are debugging from - at least not on Windows. So I made a copy of calva and ran the debugged calva there. This will not start the clsj-lib. At least not for me. |
Unfortunately shadow-cljs simply returns nothing instead of an error. |
This is using the preview of the coming Calva with that spiffy REPL Window:
Opening a ClojureScript REPL in a shadow-cljs project (Calva itself as it happens) the prompt displays:
I don't have the time right now to investigate it further, not even if the namespace really is undefined 😄, so just dumping the bug report here.
The text was updated successfully, but these errors were encountered: