Fork me on GitHub
#cljsrn
<
2018-12-18
>
bhauman16:12:11

I just release this new figwheel-bridge library

parrot 8
vikeri16:12:55

Wow! Very interesting!

vikeri16:12:43

tl;dr: Replaces re-natal with a deps workflow and better figwheel integrations?

bhauman17:12:16

it really just replaces the bridge file and rethinks it

carocad09:12:22

Habe you tried this with expo? I'm curious wether the same bridge could be used for both types of projects :face_with_monocle:

carocad09:12:45

Currently the expo template has some very specific modifications to make it work with the bridge

bhauman17:12:42

and integrates the reloading directly in the bridge root node itself

bhauman17:12:22

It will work for figwheel and figwheel-main

bhauman17:12:34

but you can effectively get a project setup from scratch

bhauman17:12:48

without re-natal

vikeri17:12:35

Very nice! Which version of RN did you run it on?

bhauman17:12:15

latest 57.8

vikeri17:12:40

Nice, did you by any chance look at production builds?

bhauman17:12:51

it doesn’t touch production builds

bhauman17:12:17

it should be out of the loop completely

vikeri17:12:38

True, looked at our project.clj and we just compile cljs normally. So I guess that part could easily be migrated to deps.edn as well.

vikeri17:12:47

Ok, nevermind. Looked at it again and realized it’s only the figwheel-bridge.js that can be included as an npm dep.

vikeri17:12:17

So we can still keep our old workflow, just replace the fighweel-bridge file with this dependency

vikeri17:12:33

Writing faster than thinking 😅

👍 4
Oliver George20:12:51

Interesting stuff

Oliver George22:12:53

@bhauman do you think it's a logical successor which could replace the re-natal figwheel-bridge? e.g. only makes things better