This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-06
Channels
- # admin-announcements (1)
- # announcements (32)
- # babashka (38)
- # beginners (91)
- # braveandtrue (1)
- # calva (1)
- # cider (9)
- # cljsrn (19)
- # clojure (129)
- # clojure-bay-area (3)
- # clojure-europe (24)
- # clojure-italy (1)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (24)
- # clojurescript (14)
- # community-development (7)
- # conjure (16)
- # cursive (3)
- # datomic (20)
- # defnpodcast (4)
- # emacs (11)
- # figwheel (2)
- # fulcro (5)
- # helix (6)
- # integrant (3)
- # jackdaw (5)
- # java (6)
- # jobs (1)
- # kaocha (13)
- # lsp (8)
- # malli (29)
- # meander (2)
- # off-topic (120)
- # pathom (3)
- # podcasts-discuss (6)
- # portal (6)
- # re-frame (27)
- # reagent (5)
- # releases (4)
- # remote-jobs (6)
- # rewrite-clj (9)
- # shadow-cljs (108)
- # xtdb (5)
Hi there! I'm currently in the process of migrating Chlorine/Clover to rewrite-clj instead of rewrite-cljs. There are some issues I'm seeing with Shadow-CLJS, for example, errors like:
rewrite-clj.node.protocols/value is deprecated
I'm literally only importing rewrite-clj.node
...@mauricio.szabo Does this happen only because of the require, or are you using some macro maybe?
No, I only required the namespace.
@mauricio.szabo, @pez https://github.com/weavejester/cljfmt/issues/224. Is this the kind of thing you are seeing too?
Yes, exactly. I'm seeing the same error: I try to import the namespace, it fails with this errors
@mauricio.szabo, fails or warns?
Warns, but on shadow-cljs by default it'll not compile with warnings, so it's almost the same as a fail :D
BTW, I changed my config to ignore warnings for deprecated functions, and it works. But as what I'm writing is a library, this can pose a problem for people consuming it...