@thheller thanks for all the tips, got it working with the plugin. One thing I noticed is that I get multiple calls to shutdown with the plugin, not sure why. Another question is can I pass arguments to the plugin from the build config? It also seems the the plugins are set globally and not per build.

@talgiat yes plugins are once per server. you can change :depends-on to :depends-on [:config] and :start (fn [config] ...)

config is the shadow-cljs.edn content

so you can add your own keys there

:sass/config {:foo :bar} or so

plugins can in theory access all server functionality and hook into anything. just none of it is documented. 😛

trying to use latest devcards, I get an error:

The required namespace "cljsjs.marked" is not available, it was required by "devcards/util/markdown.cljs".
The namespace was provided via :foreign-libs which is not supported.
Please refer to  fo more information.

@thheller thanks! I guess it’s semi documented, because I can read the source code 😁. Few other questions: so does the plugin knows which build is currently running? is it called before any build is invoked (just trying to understand the lifecycle of the whole build system and the point where plugins are called). Also did you run into cases where a plugin shutdown is called multiple times before?

Another question: can build hooks get access to the full shadow-cljs.edn content and not just the build state? (I guess I can use shadow.cljs.devtools.config/load-cljs-edn, but thought there might be something else)

@lilactown https://shadow-cljs.github.io/docs/UsersGuide.html#cljsjs

@talgiat build specific stuff should probably be in the build config which is at :shadow.build/config in the build state (passed into the hooks)

plugin is started when the runtime is started. so in server-mode once. stop should only be called when the runtime is shutdown

I need the sass/config to be visible to the plugin and for a hook

That’s why I’m asking

in the build hook you can get access to the full runtime via (shadow.cljs.devtools.server.runtime/get-instance!)

thats a map that'll contain a :your.plugin-ns/plugin key

which is the whatever was returned by :start

hello, i am following this gh issue: https://github.com/thheller/shadow-cljs/issues/250

i have created a ~/.shadow-cljs/config.edn file with the following contents

{:proxy
 {:host "localhost"
  :port 8099}}

that is the proxy configuration i use for everything

however shadow-cljs still fails to resolve the dependencies

any help is appreciated

does it work if you move the config into the shadow-cljs.edn? I changed how the global config is handled so that might not be working anymore?

i will try, please hold on

yes, that worked

thanks theller

although it is a bit unsatisfactory to have to commit my proxy configuration?

https://github.com/thheller/shadow-cljs/issues/483

great, glad ur so active!

should fix it soon. maybe a bit later. doing other stuff right now.

I'm interested in playing with shadow-cljs for a node module I'm working on, but I'm having trouble getting started with the repl. I've set the build :target to :npm-module and :runtime to :node, but after shadow-cljs watch lib and shadow-cljs node-repl I still get "No application has connected to the REPL server" when I try to evaluate forms over cider from Vim

I imagine at some point there will be a bin component to it that I can set as :main and run, but primarily I want to architect this as a library, and hope to have the normal clojure repl experience evaluating forms and executing tests.

Am I missing something?

yes 😛

shadow-cljs watch lib and node-repl are completely unrelated

if you want to REPL into teh` lib` build YOU need to launch a node process that loads the compiled code

:main is not a thing for :npm-module

what are you building?

a CLI script? a library?

Is require('./dist/whatever.core' not sufficient to load the compiled code?

it is .. but for :npm-module its a bit trickier

It’s a library that might also have a CLI mode if installed globally

eventually

so you probably want to use :node-library instead

OR in the .js files you do the require in you also require("./dist/shadow.cljs.devtools.client.node")

this is taken care of by :node-library but must be done manually for :npm-module

Oooh I see. I missed the part where it said :npm-module is intended to be part of the project

docs are a bit outdated and incomplete

if you want a normal clojure REPL experience just forget about build configs completely for now

and just shadow-cljs node-repl

and just use the :node-repl build id when selecting a REPL instead of :lib

(assuming cider/vim supports that)

Aha okay, interesting

but that is as close as you'll get to "clojure REPL"

I was able to connect to node with :node-library but I’ll also give the :node-repl thing a shot

(meaning it won't watch source files at all, or hot reload anything ever)

Gotcha

Thanks for your help!