shadow-cljs

thheller 2026-04-11T12:02:32.848839Z

quick update post for the 3.4.1 update I just released https://clojureverse.org/t/shadow-cljs-3-4-x-updates/14873

Bingen Galartza Iparragirre 2026-04-13T08:57:06.901269Z

Of course everything always worked fine when running in a Container, except that file watching didn't work at all.
🤔 We are running shadow-cljs via Docker, and we didn't have this limitation/problem

thheller 2026-04-13T09:23:49.410929Z

where are the files shadow-cljs is watching? it normally doesn't work for any mounted volumes?

thheller 2026-04-13T09:24:01.971519Z

regular filesystem might be ok

Bingen Galartza Iparragirre 2026-04-13T09:39:05.306519Z

We mount the project folder (host's filesystem) to the container

thheller 2026-04-13T09:40:00.807459Z

and you are running a watch build? I've never seen that work with automatic recompiles

Bingen Galartza Iparragirre 2026-04-13T09:40:06.104339Z

Like in the example in your blogpost, but using docker-compose

thheller 2026-04-13T09:40:07.569499Z

everything else is fine yes

thheller 2026-04-13T09:40:49.183589Z

which OS? maybe it works in linux. doesn't work for docker on macos for me, neither did windows

Bingen Galartza Iparragirre 2026-04-13T09:41:15.818069Z

We run npx shadow-cljs watch app

Bingen Galartza Iparragirre 2026-04-13T09:43:03.399239Z

We now all use Linux, so that might be

thheller 2026-04-13T09:43:51.139259Z

good to know. I mean that all just continues to work as before, nothing changes then. :polling really is just a fallback for when it doesn't

Bingen Galartza Iparragirre 2026-04-13T09:44:17.426429Z

Ok, great

Bingen Galartza Iparragirre 2026-04-13T10:52:28.858509Z

FYI: A colleague that used to work on MacOS (arm64) confirms me that hot-reloading worked as expected with the same setup.

Derek 2026-04-12T15:23:04.899959Z

It hasn't found its way to npm registry yet: https://www.npmjs.com/package/shadow-cljs

thheller 2026-04-12T17:03:25.973149Z

fixed. thx.

👍 1
scarytom 2026-04-14T13:18:53.599449Z

hot reloading has stopped working for us since upgrading to 3.4.1. We use linux with no containers.

➕ 1