I wonder if any of the leading (or maybe new up and coming) libraries/frameworks in clojurescript world are working towards support server-side rendering ala next.js? That would be really cool

Many have explored that @joshlemer, I have seen several different approaches. Here's a recent one with GraalVM embedding a cljs app inside the JVM https://nextjournal.com/kommen/react-server-side-rendering-with-graalvm-for-clojure

I also saw one doing server-side rendering with a pure-jvm-clojure implementation of an interface like reagent... removing the need to run JS on the server at all

I cannot recall the name of that one, perhaps someone else will

#fulcro has this as well https://book.fulcrologic.com/#_server_side_rendering

Nextjs does a few things in addition to that though. You can also statically render on build time and I think they also produce sitemaps. I’m pretty sure similar can be achieved with something like fulcro but I don’t think it is provided out of the box.

I generally really like this approach. There are voices that say that things like Nextjs are overkill for most of webdev. I disagree. I haven’t had a single project where requirements didn’t evolve and that includes frontend interactivity. So you end up wanting a unified and isomorphic dev environment (languages, tools) even if things start out simple. Currently exploring to leverage Clojure/Script for this. The insanity I had to deal with just this and the last week working in traditional stacks are pushing me into this direction. I have high hopes.

I have the following test that raises an exception in the go block. I know that the exception exists because it shows up in the browser, however, when I run the karma test or the browser test, it shows success (despite showing the exception in the console) Why is that and how to fix this? The exception is raised in the expression:

(.getByText screen "Sign p/Sign In")

(deftest signin-signup
    (render (r/as-element [rc/navbar]))
    (async done
      (go
        (e/init-login)
        (<p!
         (waitFor
          (fn []
            (.click fireEvent (.getByText screen "Sign p/Sign In"))
            (is (some? (.getByPlaceholderText screen "Your email")))
            (is (some? (.getByText screen "Close")))
            (is (some? (.getByText screen "Submit")))))))
           (done)))
  

@ps Is it possible that the exception occurred in the click handler?

I use clojurescript pretty extensively for my own webGL applications and I was giving someone a tutorial on the whole process. They did have one question that I couldn't answer though, and I'm sure someone here knows. What kind of negative performance impact would you see in creating something like 300 clojure datastructures representing entities versus 300 javascript objects, and what is the normal process to mitigate performance difference between the 2? I know there's advanced compilation for google closure, but is there some kind of best practice that will make sure your clojure doesn't end up weighing the program down?

Can you make the clojurescript compiler fail with an error when it reports a WARNING?