:infer-externs :auto with occasional ^js typehints works really well. I use a lot of JS libs, and it’s become extremely rare to hit a problem. JS interop with :advanced compilation used to be my #1 complaint with writing real-world clojurescript — frequent, painful, manual hunting of obscure bugs, interrupted by multiple-minute recompile times — and that whole experience is just gone now. I see an immediate warning whenever something should be hinted, I add a ^js somewhere, and just keep coding.

I'm trying to add a foreign js lib

:builds {:app {:js-options {:resolve {"libcsound" {:target :file
                    :file "resources/libcsound.js"}}}

(:require ["libcsound"]))

The required JS dependency "libcsound" is not available, it was required by "csound_wasm/core.cljs"

@hlolli what is the :target?

:resolve currently only works when using :shadow as js provider (eg. for :browser)

:node-library

:node-library just directly delegates to node require so we can't influence what that does directly

you might be able to include it with a relative path

(:require ["./libcsound" :as x]) with the file just next to the .cljs file

hmm nah that probably won't work either

spent so much time on the browser stuff I never really got to any of the node things

ok that's no problem, I fall back to js/require works fine 🙂

ah no relative might work

although it will likely try to compile with with closure which will most likely blow up

so yeah js/require might be the safest option

ok, yes I think the relative works relative to the cljs source file "../../../" pattern

I stay with js/require !

I opened this a while ago but didn’t get to it yet since I’m not sure how to resolve it properly. https://github.com/thheller/shadow-cljs/issues/131

of curiousity, you think that a node-library will perform better or worse in cljs-land when the compiled js-file is required or the original cljs source code is requried?

btw @thheller you have been an awesome help over the last few days. really appreciate you taking the time to help through some of these issues I’m having

@hlolli not sure I understand the question? cljs source code?

@lilactown np. a few people have been using shadow-cljs with macchiato already and I still want to look at the template and create one for shadow-cljs

here is one project that might help https://github.com/mjmeintjes/shadow-cljs-macchiato

Im creating a node-module in cljs code for js users, but I can theoretically use that library im creating in cljs as well. Then I'm just wondering if it's worth releasing .jar and npm package, or is npm package fast enough that it wont make a difference.

its definitely better to use CLJS code directly instead of the compiled output

question, since I’m not familiar with what-all-does-what yet: macchiato uses mount to “manage state” (still not exactly clear on what that means in context). would it make sense to use mount to manage the web server?

e.g. instead of storing a reference to the http/server obj in an atom, setup mount to manage start/stoping

no idea what mount does either sorry

😂 ok, I’ll just use an atom for now

from the template it looks like figwheel doesn’t bother with restarting the server at all

which might work but node it notorious for keeping some state in some function closures somewhere

that state wouldn’t get reloaded properly

yeah I’m pretty confused about that actually

when I tried to just drop in the core/server fn to :after-load, it complained that a server was still running on the port

but the code did reload

so I kind of assumed that figwheel was doing some kind of figgy magic to reload the server, but I really don’t know

I can’t find any reference in the template to any figwheel reload hook

so its probably just dumping in new code and hope that it works ok?

yeah ¯\(ツ)/¯

I think I actually would rather not restart the HTTP server, since that might clear out my session state

but maybe the mount magic handles that…

you don’t have to call stop/start, its just a recommendation

@lilactown fwiw, I use mount on the backend side exactly for that

@lilactown 3 components - http server (with immutant), an nrepl server, and a hikariCP instance for the database

@lilactown you can get it to not do anything on a namespace reload, for example - or you can tell it to stop and start the server - depending on what you want

(to be clear, that's with clj, not cljs on the backend, though)

but mount should behave about the same

gotcha

I’ll probably set mount up to keep track of the HTTP server as well then

it does look like it clears out my session state when I restart the HTTP server, though. which means I don’t want to restart on each hot reload

(defstate ^{:on-reload :noop} ....) should do what you want

not sure where the session state is kept but you can probably store it somewhere and re-attach on restart

but should be fine to just not restart the http server if that works for figwheel

if you dont’ want to use the the :before-load and :after-load callbacks just set :autoload true

I’m not able to see my changes to e.g. routes.cljs when I set :autoload true

does it work in fighweel?

(def routes
  ["/" {:get home}]

it does 😵 I set up a repo: https://github.com/Lokeh/shadow-cljs-macchiato

how do you add a route?

https://github.com/Lokeh/shadow-cljs-macchiato/blob/master/src/server/routes.cljs has the routes definition and https://github.com/Lokeh/shadow-cljs-macchiato/blob/master/src/server/core.cljs has the http server that creates the handler for the routes

so the server.core keeps a reference to the router. :handler (wrap-defaults router) this won’t be reloaded.

:thinking_face: I wonder how figwheel is reloading it then

trying to figure that out right now 🙂

I think its this call (mount/in-cljc-mode)

hmm nope that does nothing

I think it’s re-running the require’s at the top of app.cljs

I say, with all the authority of someone who’s done CLJS for 3 weeks

^:figwheel-always seems to be used to force reload the .app ns always

but it doesn’t do anything, the requires won’t be done again

OK, how could we set it up so that server.core doesn’t keep a reference to router?

still trying to figure out what figwheel does that I don’t

oh wait you set :autoload true in the build config. that still needs to be in :devtools {:autoload true}

it appears to work otherwise

😑 jeeze

you’re right. it works just like figwheel when I make that change

thanks for going with me on this wild goosechase 😅