I'll make a slightly more compelling example ;)

This is compelling enough for me. 😃

But, please don't let that stop ya!

I've also started experimenting a bit.

That is so awesome. Thanks for the inspiration!

@pez so this is different from Calva's existing arch in that it doesn't require a compilation step right? Also what's the difference between sci and nbb? Forgive the ignorance pls

@U037TPXKBGS good question. SCI is the Small Clojure Interpreter which powers multiple projects: babashka, nbb, 4everclojure, etc. So it is the library that enables interpretation (clojure evaluation) but each environment requires its own stuff, e.g. nbb is SCI + node.js specific stuff

For a VSCode extension you might be better off using SCI + VSCode specific stuff rather than using nbb directly, although it's worth a try.

Nbb is set up as an ES6 project using shadow-cljs target esm and this may not play so well with VSCode / electron, although I have gotten it to work using webpack.

@pez was trying to build an extension using CLJS with nbb as a dependency. For this to work you must also start with the shadow-cljs config that nbb has, I'd say (target esm for sure)

I'm curious then why @pez is exploring nbb vs sci+<something vscode specific>, or rather why one might be better off either way. Thanks!

Probably just because we can :)

@pez i wonder if this might have something to do with portal

Not related to portal. It's something we've been discussing a while here and there and now both @U04V15CAJ and I had started to experiment with it almost at the same time. I see it as a sign. 😃

That I started with creating an extension using ClojureScript is not really related either. That's more a matter of me being addicted to the developer ergonomics that the REPL gives me.