Fork me on GitHub

I have a slightly weird issue with shadow and node - I’m trying to require an npm lib, but it appears to be failing in an odd way. It works fine in a normal node repl. the values are behind proxy - could this be problematic in someway with shadow shims?


the SHADOW import error looks suspicious too!


that error you get when you run code directly in the namespace like you do


since it happens during loading of the file there is no better error to throw


the other no clue. remove the js-interop stuff, don't know what that does


log the return value of the parseHTML first, without all the get-in


Hi, I’m might be confusing myself but I’m trying to Docker compose our dev environment and run shadow-cljs in a container. But starting to realise it will be difficult to get a browser repl up in this setup or can this be done? Sorry If I’m sounding confused, but that’s kinda what I am… 🙂


that should be entirely possible if you forward the right ports between the docker container and the host. if you’re playing around, some people have success this setup: VS Code with Remote Containers + Calva Extensions. this has all the parts you need (and more) and you can find more examples, e.g. (once that is running it should be easier to make it work with plain docker)

👍 2

I am getting the following SLF4J errors if I use shadow-cljs 2.15.4 or 2.15.5 but not earlier versions:

[:app] Configuring build.
[:app] Compiling ...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See  for further details.
[:app] Build completed. (2733 files, 404 compiled, 0 warnings, 44.38s)
I have no idea how to figure out why. The code is using com.lambdaisland/glogi We were using version 1.0.116 and 1.0.128 (latest) Not sure what else would be interacting with shadow for log stuff like that. Any suggestions or known issues around this? Thanks