This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-04-07
Channels
- # beginners (166)
- # cider (6)
- # cljs-dev (12)
- # cljsrn (64)
- # clojure (71)
- # clojure-chicago (1)
- # clojure-spec (14)
- # clojure-uk (2)
- # clojurescript (25)
- # datomic (2)
- # docs (1)
- # duct (1)
- # emacs (4)
- # fulcro (5)
- # graphql (3)
- # java (46)
- # mount (5)
- # off-topic (29)
- # onyx (1)
- # portkey (10)
- # re-frame (12)
- # remote-jobs (1)
- # shadow-cljs (46)
- # spacemacs (1)
- # specter (4)
- # vim (2)
@jeaye did I understood you correctly: you don't have out of memory errors anymore? Or are the two comments about different things ?
metro=../node_modules/metro-bundler/src/JSTransformer/index.js
sed -i 's/\(TRANSFORM_TIMEOUT_INTERVAL\) = .*;/\1 = 901000;/g' "$metro" || true
This is part of my production build script, which bumps metro's time out so it can actually get through the compiled JS. With that, I can reliably build. It just takes several minutes to transform.
@jeaye thanks for the info. BTW, do you know if there is some kind of knowledge base for cljs react native?. I mean like those deep tips not general info like in http://cljsrn.org
Not that I know of @carocad. This channel is probably the best knowledge base for cljsrn.
I suspect if we had the ability to search this archive, lots of good answers are in it.
@mfikes afaik that is what https://clojurians-log.clojureverse.org/cljsrn/2017-11-14.html is suppose to be for. However since only a piece of the conversation is shown I find it quite difficult to grasp more complicated topics 😕
Definitely. That log no longer works as far as I can tell. But if it did, it would be possible at times to mine some answers.
@mfikes would you be willing to let the cljsrn-org
Wiki be the place to put those kinds of tips?
Hrm. I just created the first page. Perhaps that is enough to allow anyone to edit it now?
Ahh, it had "Restrict editing to users in teams with push access only enabled". I just turned that off.
Yeah, when something is learned, we can drop some content in there summarizing the finding 🙂
I'll add a bit near the top of http://cljsrn.org pointing to that Wiki
@jeaye if it is not too much to ask, would you be willing to put your cljs advance
compilation script in the cljsrn-org Wiki? 🙂
https://github.com/cljsrn/cljsrn-org/wiki
I just added some of the latest tips that I read over here. Hope that helps, but I cannot think of something right now that would be useful to many people besides that 😄. I guess we have to wait for the questions
Worth adding re-natal-husk there, too, along with all of the other work which has gone into the problem by frustrated cljsrn devs.
Wow. It was 3 years ago that any of this stuff even worked for the first time 🙂 https://twitter.com/mfikes/status/573918846890938368?lang=en
It's cool to see that, even though stuff is still very rough around the corners, production-quality apps are being created.
The tooling can be so ridiculously frustrating, at times, but it's a pretty great match: CLJS + RN.
In terms of performance and APK size, I'm quite pleased (as are users of our app) as well.
Yes. I recall watching what Facebook was doing, back when I was writing an app with Goby, really wanting a functional as opposed to imperative approach.
(At that time, it wasn't clear whether we would ever have something like React for native apps.)
How well do re-natal's source maps work? Are they only useful in the Chrome web tools, or also in the RSOD?
I feel like CLJSRN should have its own RSOD which is much more helpful than the default one.
We'd need to transform all of the sources before they get combined into one single mega JS file. Either before the CLJS compiler starts, or as a step in the CLJS compilation process.
metro's pretty fast at processing small files and it's built around that idea. It chokes for us because, as far as metro's concerned, we're misusing it.
In other words not the stack you'd like, like:
cljs.user=> (ffirst 1)
1 is not ISeqable
cljs.core/seq (cljs/core.cljs:1223:20)
cljs.core/first (cljs/core.cljs:1232:15)
cljs.core/ffirst (cljs/core.cljs:1744:11)
Though, for re-frame users, perhaps the best approach there is to just track the entire session's events, serialize them to disk, and upload them with the the crash report.
That way the whole session can be examined. Still, nice (or even relevant) stack traces would really help.
Well, I grew up in the south-eastern US, but eliminated most of that accent, so perhaps east coast, in general, with a little southern mixed in?
Thanks for sharing; I like being able to place accents, so I'll keep this in mind. What's there is subtle, but memorable.
Interesting, if I had to guess, my accent is probably fairly close to what you'd see on American TV / news. But of course, it is difficult for me to actually percieve that.
I'm American as well, but from every corner of the US, so my accent is a good blend of all sorts of things which I've liked from places or have otherwise stuck.