This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-05
Channels
- # aleph (90)
- # announcements (4)
- # aws (2)
- # beginners (61)
- # calva (2)
- # cljs-dev (8)
- # cljsrn (12)
- # clojars (4)
- # clojure (42)
- # clojure-europe (1)
- # clojure-finland (1)
- # clojure-greece (2)
- # clojure-houston (1)
- # clojure-italy (3)
- # clojure-nl (30)
- # clojure-spec (41)
- # clojure-uk (87)
- # clojurescript (44)
- # cursive (12)
- # data-science (11)
- # datomic (24)
- # defnpodcast (1)
- # fulcro (18)
- # hyperfiddle (1)
- # jobs (2)
- # juxt (11)
- # kaocha (3)
- # london-clojurians (5)
- # mount (2)
- # nrepl (2)
- # off-topic (9)
- # onyx (25)
- # other-languages (1)
- # parinfer (3)
- # pathom (5)
- # pedestal (3)
- # portkey (1)
- # re-frame (21)
- # reagent (24)
- # remote-jobs (7)
- # schema (2)
- # shadow-cljs (59)
- # spacemacs (5)
- # specter (7)
- # sql (9)
- # tools-deps (13)
boot-shadow has been updated to use shadow-cljs 2.8.14
ignoring obvious security holes, would it be possible to run a shadow-cljs build server on an AWS instance, and connect to the cljs-repl that is exposed? such that you can hot load CLJS code from a remote repl
@biscuitpants sure but lots of the assumptions build into the system is that files are loaded locally from disk
hmm okay, and if we had all the source on disk too? so we are only compiling new code into an existing project
so process would be: git checkout develop of our project -> start shadow build -> connect via remote repl and switch to cljs and compile
to test i guess its just a matter of running shadow and opening the port it listens on, eh?
Hmm, running into a weird bug with Maria (trying to get it using latest dependencies).
the first time I compile/watch, it works. after I make a change and recompile, on reload I get a whole pile of Namespace "goog.debug.Error" already declared.
errors from goog.provide
. I keep getting these errors even after I refresh the browser. Killing the shadow process and compiling from scratch, then it works again.
i’ve got it to happen twice in an extremely minimal project, but not in any predictable way
it somehow breaks the state, this time I was able to fix by going into the repl and manually restarting the :browser
build
well, I can semi-reliably reproduce it in Maria by starting a watch, going into a namespace and hitting spacebar + return a couple of times, then reloading the page. it’s usually (not always) broken after one or two compile cycles. I can unbreak it via (shadow/stop-worker :live)
and then (shadow/watch :live)
. it will load successfully, then break again soon after a bit of editing. i don’t have to do anything with the :bootstrap
build.
shadow-cljs watch live trusted bootstrap
with however you add the -A:release
to that
> [email protected] install /mnt/c/Users/thheller/code/oss/maria/editor/node_modules/node-sass
> node scripts/install.js
Downloading binary from
Cannot download "":
HTTP error 404 Not Found
$ shadow-cljs -A:release watch live trusted bootstrap
shadow-cljs - config: /mnt/c/Users/thheller/code/oss/maria/editor/shadow-cljs.edn cli version: 2.8.14 node: v10.13.0
shadow-cljs - starting via "clojure"
Downloading: appliedscience/js-interop/0.1.11/js-interop-0.1.11.pom from
Error building classpath. Manifest type not detected when finding deps for lark/tools in coordinate {:git/url "", :sha "113b9f6f8d8ff7a3c35864fb5f50c20be61c729e", :deps/root "tools"}
let me figure this out, haven’t seen it before but I see it is happening on circleci too
i am getting rid of the webpack thing as I wanted to deprecate that stage anyway. but I don’t know why you got the lark/tools error, that part works for me
------ WARNING #1 - :undeclared-var --------------------------------------------
File: /mnt/c/Users/thheller/code/oss/maria/editor/src/maria/live/source_lookups.cljs:117:40
--------------------------------------------------------------------------------
114 | (defn var-source
115 | "Look up the source code corresponding to a var's metadata"
116 | [{{meta-file :file :as meta} :meta file :file name :name :as the-var} cb]
117 | (if-let [logged-source (some-> (get @live-eval/evaluated-sources-by-filename meta-file)
----------------------------------------------^---------------------------------
Use of undeclared Var lark.eval/evaluated-sources-by-filename
--------------------------------------------------------------------------------
118 | (source-of-top-level-form the-var))]
119 | (cb {:value logged-source})
120 |
121 | (if-let [source-name (some-> (namespace name)
--------------------------------------------------------------------------------
`oh, i just renamed that var locally - pushed the new commit of lark/tools, 05bc43a10e8a72ba552cc87fd2794eb9db6f06c7
not seeing errors any more, and different-builds-overwriting-each-other would explain everything i was seeing
{:deps true
:dev-http {8000 "public"}
:builds {:browser {:target :browser
:modules {:app {:entries [shadow-ex.core]}}
:output-dir "public/compiled"
:asset-path "/compiled"}
:bootstrap {:target :bootstrap
:output-dir "public/js/compiled/bootstrap"
:entries [shadow-ex.core]
:exclude [cljs.js]}}}