figwheel

general discussion about figwheel, specific discussions in #figwheel-main and #lein-figwheel
practicalli-john 2019-08-01T06:07:33.011400Z

@lumpy try clearing the caches in the browse - open the dev tools and look through the settings and purge any cache you find. I used to experience the cache showing incorrect pages or getting stuck showing pages from other projects, even after restarting the browser.

lumpy 2019-08-01T12:15:48.028400Z

I have cleared all caches I can think of. Hard browser cache reset. I did a lein clean and even deleted my .m2 directory. This is not happening when we build a packaged app so figwheel must be involved. Right now only solution is to duplicate / route to /dev.

practicalli-john 2019-08-01T06:12:57.016900Z

Perhaps if you provide some details then people can start to help...

practicalli-john 2019-08-01T06:17:27.020100Z

When prompted by Cider for the build (after the prompt to select figwheel-main), use dev as the build name and not :dev

vikeri 2019-08-01T07:04:55.020800Z

Tried disabling and enabling rebel-readline, didn’t matter

vikeri 2019-08-01T07:06:13.021500Z

If I run pgrep java after a couple of failed attempts there are a bunch of lingering processes.

vikeri 2019-08-01T07:10:23.022700Z

On further investigation the REPL seems to work more reliably if I use clj -m figwheel.main.

vikeri 2019-08-01T07:26:42.023300Z

Is there a major difference between running clj -m figwheel.main and lein trampoline -m figwheel.main?

vikeri 2019-08-01T07:27:32.024Z

Apart from them using different class-paths from deps.edn/`project.clj`

lumpy 2019-08-01T12:15:48.028400Z

I have cleared all caches I can think of. Hard browser cache reset. I did a lein clean and even deleted my .m2 directory. This is not happening when we build a packaged app so figwheel must be involved. Right now only solution is to duplicate / route to /dev.

practicalli-john 2019-08-01T16:02:56.029900Z

Interesting. I always use lein fig:build to run the project.