Clojurians Log v2

@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.

That makes sense. I see a way to fix it of course but that might be more work than it’s worth.

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?

@daniel975 target needs to be on the classpath

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?

@daniel975 that’s a bug in the documentation

take the -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

@daniel975 ^

so something is amis

it looks like the server is now serving from the classpath period which is a problem

are you using ring-stack-options?