2019-09-07 12:57:22 +00:00
|
|
|
;; shadow-cljs configuration
|
2023-02-17 12:10:00 +00:00
|
|
|
{:source-paths ["src" "test/cljs"]
|
2019-09-07 12:57:22 +00:00
|
|
|
|
2023-05-31 11:35:31 +00:00
|
|
|
:dependencies [[reagent "1.2.0"]
|
2023-05-31 09:08:34 +00:00
|
|
|
[re-frame "1.3.0"]
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
[binaryage/oops "0.7.2"]
|
2023-02-17 12:10:00 +00:00
|
|
|
[com.andrewmcveigh/cljs-time "0.5.2"]
|
|
|
|
|
[status-im/timbre "4.10.0-2-status"]
|
|
|
|
|
[hickory "0.7.1"]
|
|
|
|
|
[cljs-bean "1.3.0"]
|
|
|
|
|
[com.cognitect/transit-cljs "0.8.248"]
|
|
|
|
|
[mvxcvi/alphabase "1.0.0"]
|
|
|
|
|
[camel-snake-kebab "0.4.3"]
|
2023-10-11 21:53:34 +00:00
|
|
|
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
;; Dev dependencies
|
2023-02-17 12:10:00 +00:00
|
|
|
[refactor-nrepl "2.5.0"]
|
|
|
|
|
[cider/cider-nrepl "0.25.3"]
|
|
|
|
|
[cider/piggieback "0.4.1"]
|
|
|
|
|
[re-frisk-remote "1.6.0"]
|
2023-10-11 21:53:34 +00:00
|
|
|
|
|
|
|
|
;; Use the same version specified in the Nix dependency.
|
|
|
|
|
[clj-kondo/clj-kondo "2023.09.07"]
|
|
|
|
|
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
;; We don't use the encore library, but re-frisk requires re-frisk/sente (fork of
|
|
|
|
|
;; com.taoensso/sente), which in turn requires encore. We need to bump encore to
|
|
|
|
|
;; 3.21.0+ to remove a warning displayed while shadow-cljs starts (commit
|
|
|
|
|
;; https://github.com/ptaoussanis/encore/commit/f7a21567b9611a63999609ca183c7fb175034bd6).
|
|
|
|
|
[com.taoensso/encore "3.21.0"]
|
|
|
|
|
;; Routing
|
2023-02-17 12:10:00 +00:00
|
|
|
[bidi "2.1.6"]
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
;; Test dependencies
|
2023-02-17 12:10:00 +00:00
|
|
|
[day8.re-frame/test "0.1.5"]
|
|
|
|
|
[com.taoensso/tufte "2.1.0"]]
|
2019-09-07 12:57:22 +00:00
|
|
|
|
|
|
|
|
;; port and middleware for repl in development
|
2023-02-17 12:10:00 +00:00
|
|
|
:nrepl {:port 7888
|
|
|
|
|
:middleware [cider.piggieback/wrap-cljs-repl
|
|
|
|
|
refactor-nrepl.middleware/wrap-refactor]}
|
2019-09-07 12:57:22 +00:00
|
|
|
|
|
|
|
|
;; shadow-cljs web interface
|
2023-02-17 12:10:00 +00:00
|
|
|
:http {:port 3449
|
|
|
|
|
:host "0.0.0.0"}
|
2019-09-07 12:57:22 +00:00
|
|
|
|
2020-05-14 13:00:06 +00:00
|
|
|
:cache-blockers #{status-im.utils.js-resources status-im.ui.components.icons.icons}
|
2020-05-05 05:43:55 +00:00
|
|
|
|
2022-12-20 13:57:49 +00:00
|
|
|
:builds
|
|
|
|
|
{:mobile
|
2023-02-17 12:10:00 +00:00
|
|
|
{:target :react-native
|
2023-05-16 16:42:56 +00:00
|
|
|
;; To match the folder created by Nix build of JSBundle.
|
|
|
|
|
:output-dir "result"
|
2023-02-17 12:10:00 +00:00
|
|
|
:init-fn status-im2.core/init
|
2022-12-20 13:57:49 +00:00
|
|
|
;; When false, the Shadow-CLJS watcher won't automatically refresh
|
|
|
|
|
;; the target files (a.k.a hot reload). When false, you can manually
|
|
|
|
|
;; reload by calling `shadow.cljs.devtools.api/watch-compile-all!`.
|
2023-02-17 12:10:00 +00:00
|
|
|
:devtools {:autobuild #shadow/env ["SHADOW_AUTOBUILD_ENABLED" :default true :as :bool]}
|
2023-06-22 11:25:09 +00:00
|
|
|
:dev {:devtools {:before-load-async status-im2.setup.hot-reload/before-reload
|
|
|
|
|
:after-load-async status-im2.setup.hot-reload/reload
|
|
|
|
|
:build-notify status-im2.setup.hot-reload/build-notify
|
|
|
|
|
:preloads [re-frisk-remote.preload
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
;; In order to use component test helpers in the REPL we
|
|
|
|
|
;; need to preload namespaces that are not normally required
|
|
|
|
|
;; by production code, such as
|
2023-06-22 11:25:09 +00:00
|
|
|
;; @testing-library/react-native.
|
|
|
|
|
test-helpers.component]}
|
2023-02-17 12:10:00 +00:00
|
|
|
:closure-defines
|
2023-04-27 07:53:04 +00:00
|
|
|
{status-im2.config/POKT_TOKEN #shadow/env "POKT_TOKEN"
|
|
|
|
|
status-im2.config/INFURA_TOKEN #shadow/env "INFURA_TOKEN"
|
|
|
|
|
status-im2.config/OPENSEA_API_KEY #shadow/env "OPENSEA_API_KEY"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_GOERLI_TOKEN #shadow/env "ALCHEMY_ARBITRUM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_GOERLI_TOKEN #shadow/env "ALCHEMY_OPTIMISM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_MAINNET_TOKEN #shadow/env "ALCHEMY_OPTIMISM_MAINNET_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_MAINNET_TOKEN #shadow/env "ALCHEMY_ARBITRUM_MAINNET_TOKEN"}
|
2023-02-17 12:10:00 +00:00
|
|
|
:compiler-options {:output-feature-set :es5
|
2023-09-06 11:58:42 +00:00
|
|
|
;; We disable `:fn-deprecated` warnings because we
|
|
|
|
|
;; are managing deprecation via clj-kondo and we
|
|
|
|
|
;; don't want the terminal output to be littered
|
|
|
|
|
;; with warnings on every code reload.
|
|
|
|
|
:warnings {:fn-deprecated false}
|
|
|
|
|
:closure-defines {re-frame.trace/trace-enabled? true}
|
|
|
|
|
:source-map false
|
|
|
|
|
:infer-externs true}
|
2023-02-17 12:10:00 +00:00
|
|
|
;; if you want to use a real device, set your local ip
|
|
|
|
|
;; in the SHADOW_HOST env variable to make sure that
|
|
|
|
|
;; it will use the right interface
|
|
|
|
|
:local-ip #shadow/env "SHADOW_HOST"}
|
|
|
|
|
:chunks {:fleets status-im.fleet.default-fleet/default-fleets}
|
2022-12-20 13:57:49 +00:00
|
|
|
:release
|
|
|
|
|
{:closure-defines
|
2023-04-27 07:53:04 +00:00
|
|
|
{status-im2.config/POKT_TOKEN #shadow/env "POKT_TOKEN"
|
|
|
|
|
status-im2.config/INFURA_TOKEN #shadow/env "INFURA_TOKEN"
|
|
|
|
|
status-im2.config/OPENSEA_API_KEY #shadow/env "OPENSEA_API_KEY"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_GOERLI_TOKEN #shadow/env "ALCHEMY_ARBITRUM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_GOERLI_TOKEN #shadow/env "ALCHEMY_OPTIMISM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_MAINNET_TOKEN #shadow/env "ALCHEMY_OPTIMISM_MAINNET_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_MAINNET_TOKEN #shadow/env "ALCHEMY_ARBITRUM_MAINNET_TOKEN"}
|
2022-12-20 13:57:49 +00:00
|
|
|
:compiler-options {:output-feature-set :es6
|
|
|
|
|
;;disable for android build as there
|
|
|
|
|
;;is an intermittent warning with deftype
|
|
|
|
|
:warnings-as-errors false
|
|
|
|
|
:infer-externs :auto
|
|
|
|
|
:static-fns true
|
|
|
|
|
:fn-invoke-direct true
|
|
|
|
|
:optimizations :advanced
|
|
|
|
|
:js-options {:js-provider :closure}}}}
|
|
|
|
|
;; the tests are ran with node, react-native dependencies are mocked
|
|
|
|
|
;; by using node --require override.js, which uses the node-library
|
|
|
|
|
;; produced by the target :mocks below and redefines node require
|
|
|
|
|
;; function to use the mocks instead of the rn libraries
|
|
|
|
|
:test
|
2023-02-17 12:10:00 +00:00
|
|
|
{:output-to "target/test/test.js"
|
|
|
|
|
:output-dir "target/test"
|
|
|
|
|
:optimizations :simple
|
|
|
|
|
:target :node-test
|
Upgrade shadow-cljs and ClojureScript (#15417)
This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest
2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we
can finally use the latest major Clojure version 1.11.x.
Why upgrade shadow?
- Shadow CLJS controls the ClojureScript version we can use. In order to use the
latest major Clojure version we must upgrade Shadow CLJS.
- Shadow CLJS releases new versions very frequently, and if you take a look at
its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see
it had tons and tons of bug fixes over the years. I hope some of them help
improve the DX for certain contributors who recently reported issues with
it.
- Clojure 1.11 brings new features, bug fixes and even performance improvements
(although I think the performance mostly impacts Clojure on the JVM). See the
changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110
Things that can be beneficial to us, or are interesting nonetheless:
- New :as-alias to be used in require, which is like :as but does not require
the namespace to load. This means namespaced keywords using :as-alias can't
cause circular dependency errors. This feature would very useful if we used
namespaced keywords, but we don't, so...
https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require
- New macros run-test and run-test-var to run single test with fixtures and
report.
- New iteration function, useful for processing paginated data.
https://www.abhinavomprakash.com/posts/clojure-iteration/
- New update-keys function: applies a function to every key in a map.
- New update-vals function: applies a function to every value in a map.
Examples for update-vals and update-keys. They should perform better than the
common reduce-kv approach since they use a transient data structure.
(let [m {:a 1 :b 2}]
(update-vals m inc)) ; => {:a 2, :b 3}
(let [m {:a 1 :b 2}]
(update-keys m name)) ; => {"a" 1, "b" 2}
Why change namespaces within __tests__ directories?
Any namespace with the word --tests-- throws an error, like the one below. I
didn't bother investigating why, so I changed the guidelines to reflect the new
convention. It's probably related to the double dashes in the name.
Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a
segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
|
|
|
;; Uncomment line below to `make test-watch` a specific file
|
2023-10-16 13:47:20 +00:00
|
|
|
;; :ns-regexp "status-im2.subs.messages-test$"
|
2022-12-20 13:57:49 +00:00
|
|
|
:main
|
|
|
|
|
status-im.test-runner/main
|
|
|
|
|
;; set :ui-driven to true to let shadow-cljs inject node-repl
|
|
|
|
|
:ui-driven
|
|
|
|
|
true
|
|
|
|
|
:closure-defines
|
2023-04-27 07:53:04 +00:00
|
|
|
{status-im2.config/POKT_TOKEN #shadow/env "POKT_TOKEN"
|
|
|
|
|
status-im2.config/INFURA_TOKEN #shadow/env "INFURA_TOKEN"
|
|
|
|
|
status-im2.config/OPENSEA_API_KEY #shadow/env "OPENSEA_API_KEY"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_GOERLI_TOKEN #shadow/env "ALCHEMY_ARBITRUM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_GOERLI_TOKEN #shadow/env "ALCHEMY_OPTIMISM_GOERLI_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_OPTIMISM_MAINNET_TOKEN #shadow/env "ALCHEMY_OPTIMISM_MAINNET_TOKEN"
|
|
|
|
|
status-im2.config/ALCHEMY_ARBITRUM_MAINNET_TOKEN #shadow/env "ALCHEMY_ARBITRUM_MAINNET_TOKEN"}
|
2022-12-20 13:57:49 +00:00
|
|
|
:compiler-options
|
|
|
|
|
{;; needed because we override require and it
|
|
|
|
|
;; messes with source-map which reports callstack
|
|
|
|
|
;; exceeded exceptions instead of real issues
|
|
|
|
|
:source-map false
|
|
|
|
|
;; needed because we use deref in tests
|
|
|
|
|
:static-fns false
|
|
|
|
|
:optimizations :simple
|
2023-10-04 19:06:54 +00:00
|
|
|
:warnings {:fn-deprecated false}
|
2022-12-20 13:57:49 +00:00
|
|
|
:infer-externs true}}
|
2019-09-07 12:57:22 +00:00
|
|
|
|
2022-12-20 13:57:49 +00:00
|
|
|
;; mock.js-dependencies is mocking the react-native libraries
|
|
|
|
|
;; we build it as a node library so that it can be required by
|
|
|
|
|
;; override.js
|
|
|
|
|
:mocks
|
|
|
|
|
{:target :node-library
|
|
|
|
|
:exports {:mocks mocks.js-dependencies/mock}
|
|
|
|
|
:output-to "target/mocks/mocks.js"
|
|
|
|
|
:output-dir "target/mocks"
|
|
|
|
|
:compiler-options {:optimizations :simple
|
|
|
|
|
:source-map false}}
|
|
|
|
|
:component-test {:target :npm-module
|
2023-10-17 15:27:18 +00:00
|
|
|
:entries [quo.core-spec status-im2.core-spec]
|
2023-01-13 09:35:41 +00:00
|
|
|
:ns-regexp "component-spec$"
|
2022-12-20 13:57:49 +00:00
|
|
|
:output-dir "component-spec"
|
|
|
|
|
:compiler-options {:warnings-as-errors false
|
|
|
|
|
:static-fns false
|
|
|
|
|
:infer-externs true}}}}
|
