This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-14
Channels
- # announcements (3)
- # asami (22)
- # babashka (9)
- # beginners (92)
- # calva (7)
- # clj-kondo (8)
- # clojure (60)
- # clojure-australia (3)
- # clojure-boston (1)
- # clojure-dev (3)
- # clojure-europe (24)
- # clojure-nl (3)
- # clojure-spec (4)
- # clojure-uk (14)
- # clojurescript (5)
- # conjure (12)
- # core-async (44)
- # cryogen (8)
- # crypto (2)
- # cursive (24)
- # data-science (5)
- # events (1)
- # fulcro (10)
- # garden (2)
- # graalvm (19)
- # helix (4)
- # instaparse (13)
- # lsp (13)
- # luminus (1)
- # malli (5)
- # meander (22)
- # off-topic (22)
- # polylith (8)
- # re-frame (69)
- # react (1)
- # reagent (2)
- # releases (2)
- # shadow-cljs (52)
- # sql (7)
- # test-check (3)
- # timbre (2)
- # tools-deps (9)
I need some general advice, if someone has it. I have found this https://github.com/thheller/reagent-react-native and trying to adapt it to a windows-wsl setup. I am not sure which part should be inside of WSL, has anyone done something similar that's available publicly? 🙂 I know I am asking for much, but from the answers it seems I might be better of just ditching windows for any project using react native with shadow-cljs.
why would ditching windows be a factor? I mean I use windows so I know that all the commands work fine there. don't have a clue about react-native and wsl though
given that I made the reagent-react-native
demo on windows I assume it works fine still 😉 IIRC I didn't use wsl though
wait, so everything inside windows? i have not yet tried that, using git with ssh was difficult last time
I mean I use WSL1 still so I have all the files on my windows drive and access them using windows tools
just some command line stuff I run through WSL sometimes. shadow-cljs I mostly run directly in windows. RN too because of the emulator stuff
makes total sense, I am just starting with react native (again, once I tried it several years ago), everything is new, I don't even know which bit goes where
is it possible to disable certain warnings being outputted to the console during dev builds? something like :ignore
in :warnings-as-errors
, but to disable output instead?
haha totally agree with you. its coming from an interned (no longer maintained) library, which is my reasoning
but that's a totally fair stance
I'm having some bizarre problem importing and using the npm package, which I haven't encountered before.
["date-fns-tz" :rename {format dtftz.format}]
...
(dtftz.format (js/Date.) "Europe/Berlin")
;;=>
module$node_modules$date_fns_tz$index is not defined
I upgraded the shadow-cljs version to the latest 2.14.5, but it doesn't change anything
but what else I have noticed, which may give some guidance, in this particular project also importing via
["date-fns/format" :as format]
also causes the same type of error
this is not an electron issue either, because again on a relatively clean project it works
I mean did you try this in actual code anywhere? maybe the REPL is not the best place to verify it
don't know any particulars about electron but I know they changed some security related things
I'm trying something like (js-keys dtf-tz)
to see if it even exists and what it has inside
that is checking the wrong thing if dtf-tz
is undefined
what module$node_modules$date_fns_tz$index is not defined
basically means
I don't really know what I'm checking, but I know that if it works, it spits out a list of functions, and on a clean project it works
in the browser you can easily verify it it the console since it will even autocomplete once you start typing module$...
(js-keys dtf-tz);; => #js ["format" "getTimezoneOffset" "toDate" "utcToZonedTime" "zonedTimeToUtc"]
it doesn't work in one particular project and I'm curious why and what I've messed up, especially as it has >1y and maybe I've misconfigured something somewhere