This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-15
Channels
- # announcements (13)
- # aws (6)
- # babashka (23)
- # babashka-sci-dev (6)
- # beginners (64)
- # calva (110)
- # cider (25)
- # cljs-dev (5)
- # cljsrn (8)
- # clojars (5)
- # clojure (20)
- # clojure-austin (1)
- # clojure-europe (77)
- # clojure-nl (1)
- # clojure-uk (3)
- # clojurescript (14)
- # cursive (7)
- # datahike (9)
- # datomic (13)
- # eastwood (15)
- # emacs (14)
- # figwheel-main (1)
- # fulcro (8)
- # graalvm-mobile (2)
- # graphql (2)
- # honeysql (2)
- # hyperfiddle (2)
- # introduce-yourself (4)
- # jobs (4)
- # joyride (4)
- # leiningen (4)
- # lsp (8)
- # minecraft (8)
- # off-topic (11)
- # polylith (18)
- # rdf (2)
- # reagent (3)
- # reitit (4)
- # remote-jobs (1)
- # shadow-cljs (39)
- # specter (7)
- # xtdb (3)
I wasn't able to find this out from the docs (so I'm assuming no), but is there any way to get Shadow CLJS to ingest source maps from npm packages it's leveraging?
there is no setting for this. they should be used by default but I believe it broke a couple closure compiler versions ago
We're ingesting packages we've bundled ourselves within separate repos. Shadow doesn't seem to be picking up external map files AFAICT.
Not yet, that's next step if I can't get externals working. I have to re-configure our build in our other project to do so so I was hoping they'd work externally.
this is all the closure compiler. there isn't much I can configure on the shadow-cljs side of things
Well I'll start playing with 'em to see.
I've tried multiple variations and can't seem to get inline or external source maps to work. The Closure Compiler docs say it should be possible: https://github.com/google/closure-compiler/wiki/Source-Maps Are there any special settings we can pass to closure to get these to work? It'd be a huge help for development.