This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (2)
- # alda (4)
- # beginners (15)
- # boot (89)
- # cljs-dev (88)
- # cljsrn (75)
- # clojure (149)
- # clojure-belgium (16)
- # clojure-france (2)
- # clojure-greece (6)
- # clojure-russia (108)
- # clojure-spec (39)
- # clojure-taiwan (3)
- # clojure-uk (7)
- # clojurescript (70)
- # css (3)
- # cursive (17)
- # data-science (2)
- # datascript (7)
- # datomic (41)
- # dirac (3)
- # hoplon (12)
- # instaparse (1)
- # juxt (3)
- # lambdaisland (9)
- # mount (4)
- # off-topic (6)
- # om (71)
- # om-next (4)
- # onyx (22)
- # other-languages (56)
- # perun (15)
- # proton (6)
- # re-frame (32)
- # reagent (42)
- # specter (34)
- # spirituality-ethics (7)
- # tmp-json-parsing (5)
- # untangled (13)
- # vim (4)
- # yada (6)
@drapanjanas 0.26. and it does not contain
SwipeableRow/* in node_modules, yes,
but I could not find a way to import any other
Experimental components which are present in my project's node_modulel/react-native/Libraries/Experimental.
do I need to do something extra? like wrap those in a package myself and then require by path, rather than require by name?
@misha: is it in your node_modules try to use it directly in
require, just remember that
require work from root of your app folder. For example:
(js/require «node_modules/react-native/Libraries/Experimental/<smth>»). This work on web apps, not sure this work on react-native
@savelichalex: yeah, trying that did not help either
(js/console.log (js/require "node_modules/react-native/Libraries/Experimental/Incremental.js")) (js/console.log (js/require "node_modules/react-native/Libraries/Experimental/Incremental"))
Requiring: node_modules/react-native/Libraries/Experimental/Incremental.js Requiring unknown module "node_modules/react-native/Libraries/Experimental/Incremental.js". Requiring: node_modules/react-native/Libraries/Experimental/Incremental Requiring unknown module "node_modules/react-native/Libraries/Experimental/Incremental".
@misha I was able to require
(def IncrementalPresenter (js/require "IncrementalPresenter”))
first I tried with lein build-prod it worked
yes, re-natal use-component IncrementalPresenter
you always provide same string to use-component as to require
but for me it did not work with WindowedListView because module nullthrows was not found, not sure why
@drapanjanas: now, how do I update RN in my re-natal project?
re-natal upgrade update only re-natal
no to upgrade RN you have to do it manually as per RN docs
I tried this before and get some strange bugs)
conflicts between packages
well, re-natal does not change* the RN app, so whatever there is in RN will happen 🙂
* with minor exceptions of urls
@drapanjanas: correct me if i’m wrong: when you upgrade re-natal app dependencies doesn’t update, but if i’m create new project with upgraded re-natal I get newest version of RN?
@drapanjanas: is it safe (from re-natal pov) to update to any RN versions? I am aware I might get some app code broken, but it should not break any re-natal scaffolding, right?
yes, when you upgrade re-natal you get updated scripts like figwheel-bridge.js and whatever changes in .re-natal config, but not more than that
but deps in your package.json stay untouched
maybe make cli option for this?
when you init new app with new version of re-natal you get recent version of RN in package.json so newer react-native app is initialized
@savelichalex: there is a CLI for upgrading in react-native
it should work
@drapanjanas: but when I’m create project with re-natal I doesn’t install react-naative global, isn’t it?
to create RN app init uses react-native cli, so whatever is there. no global as I know
I mean that it’s cool use just re-natal and not use
This is can just line in npm scripts in package.json to run «react-native upgrade», but run it from re-natal is cool IMO
@savelichalex: I have a different opinion, too much sugar gives you diabetes 😄
I mean, less is more, and stuff
Maybe you right, but it’s common issue for developers)
Anyway need note in readme to re-natal about it)
Just when I’m first time upgrade re-natal from cli, I thought that RN updated too
But I was surprised:smile:
yeah… its there at the bottom of Upgrading existing project, but it is invisible prrobably
I will improve that
Maybe move it right after header for upgrade
maybe two subchapters would make it more clear: upgrading React Native version and upgrading re-natal CLI
oh yeah, sounds great!
will do it this evening
@misha yes you should be able to upgrade RN version any time painlessly by following RN guide.
without upgrading re-natal itself
sweet, thanks. my main concern was about obj c code, but apparently RN cli manages that stuff, so I think I'm good.
@drapanjanas: another improvement is to write in terminal when you upgrade re-natal, that available new RN version and put link to guide
@misha: don’t forget Cmd+k in xcode 😉
@savelichalex: sure this we can do
@misha: this is clear build files
I got some dependency exceptions on rn update, so I killed node_modules folder before retrying, and x-code died, so all is good
@drapanjanas: I’ll try to do this on weekend and make PR)
But I have bad relationship with coffeescript)
@savelichalex: "Unable to resolve module emptyFunction" zzz
What is it?)
Are you trying to require direct from react-native source?)
Don’t know why ^^^ this magic works, but maybe trying to do use-component emptyFunction 😕
hm, looks like bug in RN) if search in RN repo by
emptyFunction then in all places it is 'fbjs/lib/emptyFunction'
change it directly in react-native source to 'fbjs/lib/emptyFunction'
but of course that not ideal