clsjsjs `require` compiled to absolute path

[sinistral]

I've run into a problem using CLJSJS packages in a Node.js target that I think is a boot-cljs issue: the require [cljsjs.foo] gets compiled to a cljs.core.load_file call with an absolute path, rather than a goog.require, so it can't be run outside of my development setup. It's entirely possible that I'm doing something dumb, and if so a pointer would be appreciated, with my apologies.

I don't see the same behaviour with lein-cljs, but I can't actually get that running due to other compilation issues. I have a repro case if that would be helpful.

[burn2delete]

I am running into this as well, moving the target folder out of our development container and running it in production will throw an error as none of the boot temp directories exist.

[burn2delete]

Looks like this is caused by foreign-libs being resolved to an absolute path