That’s interesting! Would be nice to have it working but for me in krell it’s been quite hit-or-miss whether things are reloaded or not.
@bhauman Almost up and running! So happy to have figwheel’s nice compile warnings again! Made me think of one thing that’s been bugging me though. It seems that compile warnings are only shown once for each problem. Is there any way to get them to bug me on each recompile?
@daniel975 here’s the deal with that, if the file that the warning came from gets recompiled you get another warning. But the cljs compiler avoids recompiling files we don’t need to so things go much faster. Hence the trade off.1
An interesting thought
That makes sense. I see a way to fix it of course but that might be more work than it’s worth.
Figured this out. My custom
index.html did not pull in the right js file.
So trying the new react native support I’m getting
[Error: Figwheel Bridge Unable to fetch optionsUrl: <http://localhost:9500/cljs-out/ios/cljsc_opts.json>]
That path exists in target/public/ so I’m guessing the figwheel root is incorrectly configured. Before I dive into trying to find out what folder figwheel is actually serving from and how to change it; is there an obvious config mistake I’m doing?
You may have to reload the app, as it may be a race condition
I do have
:paths ["src" "target"] in my deps.edn and I tried the path in the browser; it’s not resolving.
@bhauman Ok, classpath was a good hint. I needed not only target but
"target/public" on the classpath.
Actually, I think this is quite a gotcha. Have you considered keeping a list of all files that had warnings in the last compile and touching those before doing an incremental compile?
-r off of the command
Also target/public shouldn’t be the path
so that’s strange
OH that’s what you did thanks for the PR!
I only took the -r off for the production command though. In dev target/public is what did the trick. This is what my target looks like so it does add in a public directory.
yeah but the figwheel server serves from the classpath/public
so something is amis
it looks like the server is now serving from the classpath period which is a problem
Something is definitely amiss. I’m now getting the same error even with “target/public” in my path. Removing it doesn’t help but removing and then adding it back makes everything work again.
@daniel975 yeah there is something wrong with your setup.
Sorry for the delay, my son was born 10 days ago. 😊 In the end it seems completely removing target from the classpath and allowing figwheel to add it dynamically works reliably.
are you using ring-stack-options?