cljs | Easily drive GPUs from Javascript and Node.js | Runtime Evironment library

It's Saturday morning and I'm feeling lazy so I didn't run this, but this should work:

Async functions in JS are syntax sugar for functions returning a Promise.

core.async does not work with Promises by default and you need to use the helper function to make them act like channels if you want to. The macro does this for you.

It is typical to encode EDN using Transit for HTTP transfer. Support for content (HTTP body) encoding and decoding is commonplace in clients and servers.

According to the documentation for cljs-http, to POST a request using Transit+JSON i.e. content-type is application/transit+json:

$jscomp is related to the Closure Compiler and the Polyfills it creates.

It might be enough to tweak the :language-out :es6 compiler options which is somewhat similar to the :output-feature-set option used by shadow-cljs. The best way to debug this is finding the actual code that is getting polyfilled and why. Might require digging through some compiled JS though.

shadow-cljs uses the Closure Compiler more extensively than regular CLJS or figwheel but they also use it. Solutions that apply to shadow-cljs pretty much apply to other tools as well. Just the settings may work a little differently.

In your (defn init [] ...) you are creating a anonymous function and then immediately call it by having the extra parens ((fn [] ...)). So the result of that function call is what you set! as the onload instead of the function itself. Just remove one pair of parens.

In your config you are setting :optimizations and :externs in the wrong level. They need to be under the :compiler-options key. You do not need to set :optimizations at all though, they default to :advanced for browser release builds.

browser-repl starts a standalone browser REPL independenct of any build. If you want a REPL into your build use shadow-cljs cljs-repl frontend.

See http://pedestal.io/cookbook/index#_how_to_serve_static_resources. Note in particular that Pedestal's http/resource-path holds not a file-system location, but rather a URL path prefix by which Pedestal should recognize things it should redeem from the classpath.

I managed to solve the issue: Because BrowserRouter, Route and Switch aren't valid React components one has to insert them with the $ macro:

Javascript and so ClojureScript has no ArithmethicException - this test there most likely is taken from a Java/Clojure example. Dividing by zero in JavaScript gives you "infinity" (no exception thrown).

There is a clear difference between Clojure and ClojureScript what they can do and use. There are ways to use the same source code (e.g. cljc) for both platforms, but you have to deal with specifics to the platform yourself (there are reader macros in cljc to help with that).

Note: you have access to the ArithmethicException in CLJS if you are writing macros, which again are just Clojure running at compile time, but that is just a nuance to the "will never work" answer.

The easiest way to fix this is setting :compiler-options {:output-feature-set :es6}. $jscomp.inherits are the polyfills inserted by the Closure Compiler for transpiling class and other more "modern" constructs. Setting :es6 will stop that from happening. This is the best option unless you need to care about ancient browser versions.

Thanks for setting up a reproducible example. I can reproduce it with :simple, setting it to :advanced however works just fine? I have a rough idea what is happening in :simple and will see how to fix it properly.