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
nrepl / cider-nrepl deps #115
Comments
Those deps are used for production nrepl connections. The |
Sure! I overlooked this feature. Maybe it's good to add some info in readme or docs? I mean that there is some risk, that these two deps can overwrite local dev environment. For example |
Hm yes...
On one hand, it's possible that Biff's On the other other hand, facilitating At a minimum, I'll reopen this and if anyone runs into problems maybe they'll see this conversation and chime in. |
Actually I just added a "Jacking in" subsection to the getting started docs: https://biffweb.com/docs/#jacking-in. I think that'll be sufficient. |
Looks sufficient, thanks. And yes, you can connect to a running repl form emacs without any problem. The only possible issue I see is the version mismatch between cider client in emacs and cider-nrepl in case you stop upgrading the version. But I don't think you need to worry about that now. |
Yeah--even so, no matter what we do, that would be a problem when connecting to the production nrepl server, so I think might as well have the recommended path for local dev be to set deps manually if you run into conflicts. Actually it wouldn't take long to mention that in the docs. I've added it to the Jacking In section. |
Shoudn't
nrepl
andcider-nrepl
be considered as development dependencies and moved to a separate profile? Similarly to a logging issue (#114) it may interfere with local dev setup of the users of the library.The text was updated successfully, but these errors were encountered: