We've been playing around with the emmy viewer plugin here at https://github.com/reedho/scittle/ for quite some time. If we publish the plugin js output (e.g. in this case is scittle.emmy-viewers.js), it must use scittle.js from the same build or there is build config so that we can use official scittle.js while using our plugin .js files?
you must use the scittle.js from your own build, due to how Google Closure optimizations work
I believe the plugin js size not affect main scittle.js much, is it good idea to have this plugin bundled from scittle build. @daslu probably want to do this? or do you have other suggestion?
From my perspective, of course it would be great to bundle it with the usual scittle build. This way, users will not need to bother about build anything, but simply use it in their HTML files.
This has come up before. The hoplon folks wanted to do the same, but I'd rather not maintain the whole clojure-verse, this is why I wrote the plugin system. Issues with your project will always first reach me if it's part of the standard bundle, it's just how it is I'm fine with your SCI config to live in https://github.com/babashka/sci.configs/tree/main/src/sci/configs but I'm not prepared to deal with "production" issues of your plugin
Also you won't be limited by me including more libraries and tools to your liking
I can see the bright side. I was also initially looking for some suggestion on how the naming should be implemented, if, for example we want to distribute via jsdelivr too.
or @your-org/scittle-whatever
I see, i will take a look. Thank you so much.
Makes sense, many thanks