@dnolen: the cljs shim currently injects script tags with relative paths into the html without taking into account where the executing cljs file was loaded from. Do you think it’s worth making this work when loading the shim from a different location than where the shim is hosted? (i.e. shim and other cljs is hosted on localhost:4000 while the HTML file that loads it is hosted on localhost:3000)

if(typeof goog == "undefined") document.write('<script src="app.out/goog/base.js"></script>');
document.write('<script src="app.out/cljs_deps.js"></script>');

@martinklepsch: In IE it falls back to how it currently works?

@juhoteperi: that’s what I assume but haven’t tested

var base = document.currentScript.src.split("app.js")[0] || "";

@martinklepsch: what's the rationale here? serving different files from different ports just seems gratuitous

@dnolen: there's an existing application and in development it’s easier to serve cljs from another http server than integrating it into the existing app

@martinklepsch: :asset-path is usually an absolute path, why can’t you just set it to the full path?

@dnolen: you’re totally right, stupid mistake on my side. Should have checked the shim generating code first.

ha, not a stupid mistake, happy that :asset-path suffices