can someone tell me in this example: https://github.com/reagent-project/reagent/blob/363f2d4976ac077a289d7a5d46d41a22e15d723c/examples/material-ui/src/example/core.cljs#L4

(:require [reagent.core :as r]
          ["@material-ui/core" :as mui]

that's an npm organization

so the actual npm package is "@material-ui/core"

but what’s the reasoning? Why?

because that's how the material-ui org published it to npm. 😄

https://docs.npmjs.com/about-scopes

Ah… now that explains… Thanks!

also npm modules have to be required as strings rather than symbols

(if that helps any in explaining the difference :))

Symbols can be used for npm modules, so long as a legal symbol can be used. Strings are sort of an "escape hatch" when symbols can't be used to identify a library. (This could be thought of as a general thing, not specific to npm.) As an illustrative example, it is perfectly fine to (require '"clojure.zip") in a REPL.

AH! that's good to know

thanks @mfikes

@mfikes I saw https://gist.github.com/mfikes/9fc981ed7a190b8e9b2912eee98fdd5e. Is there some way to deal with bigints today without using something as drastic as a cljs fork? I'm using cljs-ajax to get edn and the reader rounds my large integers

Sure, you could just use regular JavaScript interop. That gist is an experiment to see what it might mean to have them "integrated" into the language. But there is nothing stoping you from using them via interop today.

Not sure what to do about edn reading though...

Maybe use transit with custom handlers for bigint