Configuration for cache busting URL about lein-figwheel HOT 3 CLOSED

Hey Joel,
I was just looking at ankha the other day. Also, I just looked at your page and saw Shodon. Damn, wish I had known about that a while ago.

Anyway, I think I have a solution for this problem. The thing is, you are connecting to the websocket server correct?

That same server is serving the static files, so I think the thing to do is to get the hostname for the files that are being loaded from the :websocket-url and then load the files from the websocket server as a rule. There is a high probability that this will work for most cases because the websocket connection has to be there in the first place. I should have written it like this from the beginning, it would have saved a lot of headaches.

Working on a fix right now.

If you don't think this will work for you, let me know.

from lein-figwheel.

I added a :url-rewriter option that takes a function which will be passed the full asset request url of javascript files and css files. I also modified the client so that it defaults to loading files from the host of the :websocket-url so this may obviate your need to use the :url-rewriter.

from lein-figwheel.

Also, I just looked at your page and saw Shodon. Damn, wish I had known about that a while ago.

Thanks for the hat tip. Ankha has turned out to be more useful than Shodan (which has several patches I still need to push from other projects) but both can be very helpful for debugging. I guess I'm just not a big fan of (println what-the-heck?). 😆 Feel free to send me a patch if you have ideas!

Figwheel has turned out to be a really awesome tool for me. Paired up with a Weasel REPL you just can't beat it.

I added a :url-rewriter option that takes a function which will be passed the full asset request url of javascript files and css files.

Awesome! That's exactly what we need. I really appreciate it! Looking forward to the release (if you haven't cut it already!).

from lein-figwheel.