This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-04
Channels
- # aleph (10)
- # announcements (2)
- # babashka (2)
- # beginners (101)
- # calva (17)
- # cider (11)
- # clara (6)
- # clj-kondo (25)
- # cljsrn (33)
- # clojure (181)
- # clojure-dev (15)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-nl (8)
- # clojure-uk (22)
- # clojurescript (111)
- # clojutre (58)
- # cursive (31)
- # data-science (1)
- # datomic (10)
- # emacs (6)
- # ethereum (1)
- # fulcro (20)
- # graalvm (3)
- # jackdaw (5)
- # leiningen (5)
- # off-topic (31)
- # re-frame (2)
- # reitit (10)
- # shadow-cljs (9)
- # spacemacs (16)
- # sql (8)
- # tools-deps (16)
- # vim (17)
@jgoodhcg no idea. I don't do regular react-native development so I'm not familiar with the tooling. it might try to process the generated code via babel which is known to take a long time so maybe excluding it might help.
Since jest runs with a release compile and the release compile generates 175 files
[:test] Build completed. (175 files, 1 compiled, 0 warnings, 30.54s)
But jest fails with a watch compile and the watch compile generates 242 files
[:test] Build completed. (242 files, 2 compiled, 0 warnings, 6.91s)
I'm curious what the difference is between the two sets of artifacts? @thheller:preloads
? meaning stuff only added to builds during development. for watch that'd be the devtools stuff
I didn't have any preloads set up for either of the two builds in this project.
:builds
{:app
{:target :react-native
:init-fn
:output-dir "app"
:devtools {:autoload true}}
:test
{:target :npm-module
:output-dir "test-out"
:devtools {:enabled false}}} ;; JUST added this and testing now
Yea if I can't get this working with the next few attempts I'll just limit myself to only using release compilation for these tests.
Not sure how to do that. The only explicit babel thing is this file babel.config.js
at my project root.
module.exports = function(api) {
api.cache(true);
return {
presets: ['babel-preset-expo'],
};
};
Doesn't seem to run the tests with that
test-out/time_align_mobile.handlers_test.js
● Test suite failed to run
babel-jest: Babel ignores test-out/time_align_mobile.handlers_test.js - make sure to include the file in Jest's transformIgnorePatterns as well.
Maybe I should include anything with _test
in the name? Or not ignore it?maybe its enough to exclude some of the bigger files only. so cljs.core.js
and so on
@jgoodhcg I did that example using jest and I use watch but did not got the heap limit error. But my machine has 16gb of ram so that could explain why.
I only get the heap limit when I include one of the namespaces I want to test. Machine has 32gb of ram and I've used node options to explicitly give the process up to 4.
So it might be that I'm including some library that doesn't play well when compiled with watch.
The repo is public btw https://github.com/jgoodhcg/time-align-mobile. If you wanted to see what the compiled code was.