This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-13
Channels
- # announcements (1)
- # babashka (30)
- # beginners (43)
- # biff (24)
- # calva (72)
- # cider (12)
- # clj-commons (24)
- # clj-on-windows (10)
- # cljsrn (23)
- # clojure (123)
- # clojure-bay-area (6)
- # clojure-europe (43)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-uk (9)
- # clojurescript (125)
- # core-async (9)
- # cursive (2)
- # data-science (3)
- # datomic (30)
- # devops (1)
- # emacs (13)
- # events (5)
- # fulcro (15)
- # graalvm (3)
- # gratitude (1)
- # humbleui (11)
- # lsp (5)
- # nbb (24)
- # off-topic (11)
- # pedestal (5)
- # releases (1)
- # remote-jobs (1)
- # sci (15)
- # scittle (16)
- # shadow-cljs (15)
- # sql (11)
- # tools-deps (9)
- # xtdb (5)
Working on deps stuff in Maria and wondering about how to handle
1. module splitting (lazy loading of compiled cljs) eg using https://clojureverse.org/t/shadow-lazy-convenience-wrapper-for-shadow-loader-cljs-loader/3841
2. dynamic import of js, eg using https://shadow-cljs.github.io/docs/UsersGuide.html#_dynamic_module_import
Could we allow load-fn to return a :context-opts
argument which would be merged into the sci context in order to fulfill the require, as an alternative to source code? then I could lazy-load cljs or dynamically load js in the background + pass back just the sci config that I would have supplied initially, had that code been part of the original bundle. Or maybe there’s already a different way to do this
@mhuebert Have you read this yet? https://github.com/babashka/sci/blob/master/doc/async.md
nbb also lazy-loads pre-compiled modules so it doesn't have to load everything in advance
I do have this: https://clj-kondo.michielborkent.nl/ but it's powered by a backend which runs the clj-kondo binary