-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Connecting to an out-of-process nREPL server and a merged Figwheel-main build #1386
Comments
We structure builds this way:
This allows us to do this for a production deploy, as a merged build:
Only vanilla So for development we merge (defn start-cljs-repl []
(let [read-build (figwheel.main.api/read-build "common" "local")
build-id (:id read-build)]
(try
(figwheel.main.api/start {:mode :serve} read-build)
(figwheel.main.api/cljs-repl build-id)
(catch RuntimeException _e
(println "The build is already running, connection to the REPL only")
(figwheel.main.api/cljs-repl build-id))))) |
Thanks. It is strange that the built-in Figwheel Main sequence doesn't work for connecting to Anyway, I pushed a PR to that reoro, containing a custom repl connect sequence, that simply calls your "calva.replConnectSequences": [
{
"name": "My local build",
"projectType": "deps.edn",
"cljsType": {
"dependsOn": "Figwheel Main",
"connectCode": "(start-cljs-repl)",
"isConnectedRegExp": "To quit, type: :cljs/quit",
"buildsRequired": false,
}
}
] Not sure the last two settings there are required. You can experiment with removing them and see if it works anyway. |
As discussed with @PEZ on Slack:
The README.md in this repo explains the ideal workflow: https://github.com/danieroux/calva-clojurescript-usage
The less magic, the better ;-)
The text was updated successfully, but these errors were encountered: