I have a cljs project (`first project`) with the following shadow-cljs.edn -

{:source-paths
 ["src"]

 :dependencies
 [[re-frame "1.3.0-rc3"]
  [com.degel/iron "0.4.0"]]

 :builds
 {:library
  {:target :node-library
   :output-to "out/re_frame_firebase.js"
   :exports {:initializeApp com.degel.re-frame-firebase.core/initialize-app}}}}

[:app] Build failure:
The required JS dependency "re-frame-firebase/out" is not available, it was required by "app/fb/init.cljs".

$ ls node_modules/re-frame-firebase/out
re_frame_firebase.js

How can I call a function in a dynamically loaded module? Edit: nevermind; resolve did the trick

@murtaza52 you absolutely should not be including a compiled CLJS build in another CLJS build. just include the sources directly instead

@wombawomba how are you loading the module? avoid resolve if you can, it is not ideal.

https://clojureverse.org/t/shadow-lazy-convenience-wrapper-for-shadow-loader-cljs-loader/3841

@thheller I'm using shadow.loader/load

shadow.lazy looks really useful — thanks!

you should include it in the user's guide

https://code.thheller.com/blog/shadow-cljs/2019/03/03/code-splitting-clojurescript.html is also an option

lazy-component helper based on shadow.lazy

(if you are using react)

@thheller this is a third party library (`re-frame-firebase`), that we are using in a project. We had to fork it make changes to it. (we converted it to a shadow-cljs project) Now I am having trouble using it in my project ? As you suggested include the sources, you mean just copy all the sources in the project, or is there a better way ? (bcoz that will defeat the purpose behind having libraries)

you can package it as your own library

or include it from a local directory

or use deps.edn and use a git dependency

many options, dunno what exactly you need but I including a compiled version is definitely the last thing you should be doing

if the changes you made are only done for your second project it is fine to include the sources directly too. no point in writing libraries with exactly one consumer 😉

@thheller thanks that is what we were trying to do - include it from a local directory

this is the dep entry in package.json for the second project "re-frame-firebase": "file:../re-frame-firebase",

and npm install includes the compiled version along with sources under the node_modules

no, that is not what you are doing. I mean yes, but you are trying to include the wrong thing

CLJS libraries are never compiled, they are included from source only

so you should do the same. include the source

you can do so via shadow-cljs.edn by adding :source-paths ["src" "../that-library/src"]

@thheller thanks for that blog post. It's pretty much exactly what I was trying to build :)

or publishing that modified lib to clojars (pretty easy if it is already using leiningen)

and then just adding it as a regular dependency

aah so I should never use it via package.json through npmjs . But why at the end its a regular js file, how does it matter if I distribute it via clojars (jar) or npmjs (node module) ?

the compiled version will include its own version of firebase, reframe, cljs.core and whatever else it is using. it will not be compatible with the one you are using in your project.

ok thanks. so If I do a lein install on the re-frame-firbase (first project), the jar will just include the sources, and then the shadow-cljs in the second-project will compile it to js ?

yes

great, thanks, let me try it out

heya! is there a way to write a macro that will expand to a (def ^:export ...) ?

I’ve tried this:

(defmacro defoo [name]
  `(def ^:export ~name 42))

(defoo bar)

myns.bar = (42);
Object.defineProperty(module.exports, "bar", { enumerable: false, get: function() { return myns.bar; } });

looking at the shadow-cljs code, it should be enumerable: true if the def is exported

I’ll answer myself – this works:

(defmacro defoo [name]
  `(def ~(with-meta name {:export true}) 42))