Thomas Heller

Hmm I don't have any guesses for you. Segmentation faults are way beyond my expertise and can be caused by pretty much everything in a System (eg. faulty RAM). Does...

Only guess I have is related to this one https://github.com/google/closure-compiler/issues/3945. You appear to be using highlight.js via 10x, so maybe on your particular OS/JVM combo it just segfaults instead of...

Leaving this open until I can figure out how to handle this properly. Currently the Closure Compiler is used in many places, not just for optimizations. So all these places...

This is currently at the lowest possible priority given that the current only cause I know of is a file in highlight.js that 99.9% of people probably don't need anyways....

Sorry, I do not understand what this is about. Please clarify and provide an example.

Frameworks such as remix or nextjs do require custom file layouts. In shadow-cljs this would be covered by implementing a custom `:target` for those platforms. I did [some experiments](https://clojureverse.org/t/creating-websites-with-shadow-cljs-gatsby-or-next-js/2912 in...

I haven't used Astro, so this is all based on glances of the docs. I don't think its a good match for CLJS (and shadow-cljs), given that they really need...

Different devtools implementations can be picked by setting a different `:runtime` in the build config. It just defaults to the browser and in this case doesn't actually mean browser but...

Uhm I don't have any guesses as to what might be causing this. I guess to debug this you can open `shadow-cljs clj-repl` and then eval this ```clojure (alter-var-root #'shadow.build.npm/find-resource-in-package...

I would assume that the `test.js` file isn't actually required when used in a build? But `../` is also a perfectly fine require. Just `"."` isn't but I'm unsure where...