This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-04
Channels
- # announcements (9)
- # babashka (5)
- # beginners (50)
- # calva (13)
- # clj-kondo (11)
- # clojure (30)
- # clojure-australia (1)
- # clojure-china (1)
- # clojure-europe (4)
- # clojure-filipino (1)
- # clojure-hk (1)
- # clojure-indonesia (1)
- # clojure-japan (1)
- # clojure-korea (1)
- # clojure-my (1)
- # clojure-norway (2)
- # clojure-sg (1)
- # clojure-taiwan (1)
- # clojurescript (32)
- # conjure (2)
- # honeysql (1)
- # hyperfiddle (8)
- # jobs-discuss (9)
- # leiningen (2)
- # malli (3)
- # off-topic (21)
- # reitit (4)
- # shadow-cljs (10)
- # sql (3)
- # squint (17)
- # tools-deps (14)
@thheller such a long time since we've chatted. You may not even remember me. Of course, like a bad relative, I'm here because I need your help
I'm trying to use https://shadow-cljs.github.io/docs/UsersGuide.html#_conditional_reading as part of my Calva/vscode setup and have a couple questions:
1. do these conditionals work when deploying a library that should work in both node and the browser (i.e., runtime) or are they a compiled feature?
2. do they work when using them w/a REPL (mine currently = vscode + calva) without setting anything in the config
?
hey, they are a reader feature. so they'll work as long as the source code is read somewhere, but only during reading. as such without config they'll not trigger if you add custom conditionals?
understood. I'll find another way. Good to hear from you again old friend
probably because since it's not officially supported
correct. they do work just fine but they must have a reason for rejecting them from official support 😛
are there any build constants that could be used for conditional build?
i found :closure-defines