This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-19
Channels
- # aws (2)
- # babashka (4)
- # babashka-sci-dev (7)
- # beginners (92)
- # biff (7)
- # calva (64)
- # cider (2)
- # cljsrn (14)
- # clojure (8)
- # clojure-australia (5)
- # clojure-europe (14)
- # clojure-norway (8)
- # clojure-spec (36)
- # clojurescript (19)
- # component (15)
- # cursive (1)
- # data-science (6)
- # girouette (5)
- # hyperfiddle (3)
- # juxt (5)
- # leiningen (10)
- # lsp (7)
- # malli (12)
- # nbb (90)
- # polylith (1)
- # portal (11)
- # rdf (7)
- # reagent (6)
- # reitit (40)
- # remote-jobs (1)
- # shadow-cljs (21)
- # specter (5)
- # squint (83)
- # tools-deps (17)
- # vim (7)
So I blinked and now it seems react native components are published as pure typescript. Is that something we support=
@U050B88UR quick sanity check. Do you think Krell will work with a node module which only includes typescript source files? In this case seems like krell doesn't generate the require statement when the node module "main" is "src/index.ts" My suspicion is that there's a file type filter somewhere (perhaps in the cljs source code) and ".ts" is not whitelisted. In the realm of React Native this seems supportable because the metro bundler translates for us.
Thanks for coming back to it. My suspicion is that the Metro bundler isn't involved in collating the npm requires. That the https://github.com/vouch-opensource/krell/blob/master/src/krell/passes.clj#L61 (not krell code) doesn't pass through npm deps with expected data. I should be able to prove that but currently wrestling with React Native / Mac M1 compatibility issues.
that’s for assets only pretty sure, I think we just rely on ClojureScript for unresolved nses coming from node_modules
I feel you
https://github.com/react-native-image-picker/react-native-image-picker/blob/main/package.json
We need a major version upgrade due to compatibility issues with Android API 30
Seems like we could work around by forking and converting the TS back to JS.
But perhaps we're missing some common approaches used by others.
they have always been published as various kinds of non-actually JS. nothing new really. doesn't affect CLJS in any way either since you've always been running through metro which handles that
thank you