Closed wodin closed 2 years ago
@wodin sorry for the delay - I've added a thing to master to make this easier in a couple of ways. There's now a command line flag to supply custom index.js on the classpath - and for people who want to compose some kind of template (without forcing users to supply args) - we try krell_index.js
before defaulting to index.js
.
Please give it a try. If it works for you we can close this.
Yes, this works. I copied the patched index.js
to src/krell_index.js
and that was used to generate the correct index.js
.
This took me a while to get working because I couldn't work out how to get krell to connect to the right IP address. The last time I tried it it connected to my VPN IP address. This time it was connecting to a docker IP, so I could not just start my VPN to get things working.
Part of the problem was because I didn't realise that the --host
option is silently ignored if you do this:
clj -M -m krell.main -co build.edn -r --host blah
I eventually worked out you have to specify it during the compile step.
@wodin great! I'll cut 0.5.3 tomorrow.
Hi
I got Krell working in an Expo app. The main thing you need to do is build with EAS Build instead of the "classic" build system. It's useful to install
expo-dev-client
too.The only other thing you need to do is patch the generated
index.js
something like this:As you said on twitter, "it would be nice for example to allow anyone to write tiny Krell extension lib that injects what is required".
Thanks :)