This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-23
Channels
- # announcements (12)
- # beginners (225)
- # calva (7)
- # cider (45)
- # clj-kondo (1)
- # cljdoc (1)
- # cljsrn (3)
- # clojure (112)
- # clojure-dev (45)
- # clojure-europe (6)
- # clojure-finland (2)
- # clojure-india (1)
- # clojure-nl (27)
- # clojure-spec (37)
- # clojure-uk (171)
- # clojurescript (39)
- # core-async (9)
- # cursive (22)
- # datascript (8)
- # datomic (50)
- # emacs (12)
- # figwheel-main (17)
- # fulcro (42)
- # garden (2)
- # hoplon (27)
- # jobs (4)
- # kaocha (8)
- # klipse (2)
- # luminus (2)
- # off-topic (9)
- # perun (33)
- # planck (2)
- # re-frame (9)
- # reagent (48)
- # reitit (5)
- # remote-jobs (1)
- # rum (2)
- # shadow-cljs (23)
- # slack-help (3)
- # spacemacs (18)
- # sql (7)
- # tools-deps (24)
- # unrepl (9)
- # vim (30)
Has anyone here gotten the
demo to work with msys2?
@hlolli the way the current :react-native
target works seems to be the only one thats reliable enough. the re-natal/figwheel-bridge approach also works ok-ish but the problem I found with that is that initialization becomes async. so you have to render a temporary "app is loading" component and then swap in the real one once it is loaded
and also causes problem for things like react-native-navigation
as far as I understand it
stacktraces, and clojure compile errors (hud), they would come hand in hand with a source map support?
Hello, is there a way to require json files, doing something like this (:require ["./multisig-abi.json" :as multisig-abi])
?
Maybe JSON.parse
from javascript would help? It would give you a js object which you can pass through js->clj
if needed.
I'll have to first read the file from disk then, any suggestions on how to do that without having to for example evaluate clojure at compile time by wrapping slurp in a macro ?
I found this though maybe it’s useful? https://clojureverse.org/t/using-none-code-resources-in-cljs-builds/3745
hi there, newbie-ish q about the cljs compiler. I might be asking this in the wrong place, but using shadow to do my compilation so figured I’d try this channel first.
is there a way to bundle all generated code up in a single file (like in advanced optimizations), except with no optimizations applied?
I’m outputting a node script that’s preloaded on electron webviews. closure modules in non-advanced comp modes try and resolve deps based on relative paths, which doesn’t work in this case as there’s a separate hostname prepended to every dep load.
e.g. an output with a main fn in /my/local/lib.js
which requires /my/local/dep.js
is preloaded onto
. when /my/local/lib.js
tries to load /my/local/dep.js
, it does so as
.
apologies if that’s a bit confusing. please let me know if so and I can clarify. if anyone has any ideas for how to solve this besides just programming w/ advanced mode turned on, I’m all ears
I recall thheller was working on a :single-file
bundle option for node scripts but I think he ran into some blockers
@mss you can set :devtools {:loader-mode :eval}
which creates a single file. you'll need to use the :target :browser
though since :node-script
isn't really the correct target for webviews. see https://clojureverse.org/t/improving-initial-load-time-for-browser-builds-during-development/2518