This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-24
Channels
- # announcements (1)
- # babashka (86)
- # beginners (75)
- # boot-dev (1)
- # cljdoc (18)
- # cljs-dev (1)
- # cljsrn (67)
- # clojure (127)
- # clojure-australia (1)
- # clojure-dev (2)
- # clojure-europe (9)
- # clojure-nl (2)
- # clojure-serbia (2)
- # clojure-spec (11)
- # clojure-uk (14)
- # clojurescript (17)
- # code-reviews (4)
- # conjure (37)
- # core-async (11)
- # datomic (21)
- # emacs (1)
- # helix (36)
- # jobs (6)
- # malli (1)
- # meander (20)
- # re-frame (13)
- # reagent (49)
- # remote-jobs (11)
- # rum (1)
- # sci (1)
- # shadow-cljs (29)
- # sql (17)
- # vim (2)
Does shadow infer externs for JS libraries required from a file system? Seems like methods got renamed, but there’s no warnings about failed externs inference
there is no inference for JS files, since that is only part of the CLJS compiler which they don't go through
makes sense, is there anything shadow/closure can do to warn about renamed symbols in JS files?
hello. Does the possibility exist to create a working setup whereby node would be running on something like say a raspi-zero that can run node, connected to a regular development system that can reasonably run JVM/Shadow/node, and be able to create a repl experience, or is that folly?
that is trivial if you use something like sshfs or so. something that makes the files from your PC available over on the pi
lets say :node-script
you have :output-to "out/script.js"
and :output-dir "out"
. you somehow make the out
directory available on the pi and run it there via node script.js
or so
then the only extra option you'll need is :devtools {:devtools-url "
in your build config
seems like this is pretty close to working. Had to stuff a 'ws' on the target device. So I'm running 'watch app' on the dev box, and running app with node on the target. It clearly gets a code reload whenever the watch decides to recompile.
calva just talks to your dev box and the shadow-cljs process handles the messaging between the processes
https://shadow-cljs.github.io/docs/UsersGuide.html#repl-troubleshooting maybe that helps a little
I tried to validate that with a fs.writeFileSync, and I don't seem to see that behavior
how did you start the REPL though? if you juse use node-repl
that will run on the dev box