This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-30
Channels
- # aws (4)
- # beginners (143)
- # boot (37)
- # cider (31)
- # cljs-dev (53)
- # clojure (303)
- # clojure-conj (5)
- # clojure-dev (106)
- # clojure-dusseldorf (2)
- # clojure-greece (3)
- # clojure-italy (23)
- # clojure-spec (83)
- # clojure-uk (7)
- # clojurescript (328)
- # core-async (25)
- # cursive (2)
- # datascript (2)
- # datomic (3)
- # emacs (10)
- # hoplon (1)
- # jobs (2)
- # lein-figwheel (1)
- # leiningen (13)
- # luminus (6)
- # off-topic (38)
- # onyx (2)
- # parinfer (13)
- # pedestal (2)
- # portkey (5)
- # re-frame (11)
- # reagent (2)
- # shadow-cljs (61)
- # specter (6)
- # unrepl (60)
- # vim (4)
Hi, Noob question. I'm using Cursive and fallowing the instructions in the fulcro-lein-template
. Build works, hot reload works, repl seems to work for stuff like "(+ 1 2)" but not (js/console.log "test") -> No such namespace: js,
. Am I doing something wrong or is this the way it's supposed to work ?
Hello
Is any way to start a watch and a repl on a single operation ?
I just want to report that :reload
still not work
@rdanielo https://shadow-cljs.github.io/docs/UsersGuide.html#_clojure_repl or https://shadow-cljs.github.io/docs/UsersGuide.html#clj-run can be used to start watch+repl
But those methods are for spawning an standalone repl, I want to launch a watch and a repl attached to it.
Well, it may be something related to my setup
Or how do I use it
Can you describe the correct steps to reload a file and then execute the functions within it ?
I am really missing the haskell :load
functionality
@thheller do you know if this is a bug or if I'm doing something wrong?
The required namespace "mranderson047.reagent.v0v8v0_alpha2.reagent.core" is not available, it was required by "day8/re_frame_10x/view/event.cljs".
"mranderson047/reagent/v0v8v0_alpha2/reagent/core.clj" was found on the classpath. Should this be a .cljs file?
There is a clj and a cljs file with the same name.But those methods are for spawning an standalone repl, I want to launch a watch and a repl attached to it.
(ns cljsjs.react-highlight
(:require ["react-highlight.js" :as react-highlight]))
(js/goog.exportSymbol "Highlight" react-highlight)
(ns cljsjs.highlight.langs.clojure
(:require ["highlight.js" :as highlight]
["highlight.js/lib/languages/clojure" :as c]))
(.registerLanguage highlight "clojure" c)
You will need the other one too. But all of those are not really tested because compilation failed before I could check
https://github.com/Day8/re-frame-10x/blob/react-16/src/day8/re_frame_10x/view/event.cljs#L6
so mranderson047.reagent.v0v8v0-alpha2.reagent.core
is available but mranderson047.reagent.v0v8v0_alpha2.reagent.core
is not
do you still want to open the PR for those namespaces above so you get the "credit" (whatever that means)?
I will check if those are even working before opening the pr. I can do that now that the project is compiling.
this doesn't really apply to shadow-cljs since your build decides what goes into it. not your dependencies.
eg. :preloads
are not included in a release
build therefore if doesn't matter if you have them on the classpath
Can you take a look at https://github.com/Day8/re-frame-debux#two-libraries ? It's a dependency only for side effects on clojurescript.
It replaces the implementation of a tracing version of defn
and fn
but I'm not sure about how to do that using shadow.
I don't get what is happening. why is that split into two libraries. the runtime overhead of doing one thing or another in the macro is tiny.
The macro that is created is pretty large, when you expand it out. We made two libraries so you didn’t need to include any of the dev dependencies and you could be 100% sure there was no extra code ending up in your prod build
I have a feeling the :devcards true
trick will not be safe under the new AOT cache?
I’m happy to hear other approaches for solving this problem
I think I'm missing something simple here. Why wouldn't a closure define work to make the macro do what is done in the two libraries separately?
We make the separate stub library so that you can be absolutely sure that the extra code doesn't get included
The DCE does ensure that, but this felt like a safer way to do it
You don't have to use the tracing-stubs library I guess, as long as the closure-define isn't set
It will default to not running
Yeah, I see what you mean but shadow doesn't have a native way of having different development/production dependencies, I would have to add another tool for that.
Sure, we’ll you should be fine just using the tracing library then
> With this setup, your use of both macros will have zero runtime and compile time cost in production builds, and are able to be turned off at dev time too via the Closure define. This ensures that you can leave your code instrumented at all times, but not pay any costs in production.
Let me try to invoke @danielcompton about this 🆙