This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # aws (1)
- # beginners (30)
- # boot (7)
- # cider (52)
- # clara (91)
- # cljs-dev (33)
- # cljsjs (1)
- # clojure (447)
- # clojure-brasil (3)
- # clojure-dev (16)
- # clojure-dusseldorf (5)
- # clojure-filipino (1)
- # clojure-italy (29)
- # clojure-sanfrancisco (5)
- # clojure-spec (62)
- # clojure-uk (37)
- # clojurescript (145)
- # clojurewerkz (1)
- # code-reviews (12)
- # community-development (157)
- # cursive (5)
- # datascript (1)
- # datomic (27)
- # editors (42)
- # emacs (5)
- # fulcro (31)
- # hoplon (2)
- # jobs (2)
- # keechma (1)
- # lumo (31)
- # off-topic (2)
- # om (1)
- # onyx (13)
- # parinfer (8)
- # re-frame (13)
- # reagent (32)
- # remote-jobs (4)
- # shadow-cljs (103)
- # spacemacs (15)
- # specter (10)
- # sql (1)
- # tools-deps (35)
- # unrepl (13)
ugh. so I have to use a charting library that’s depending on cljsjs/react 16^, but the latest version of reagent depends on cljsjs/react 15^
yea I saw that, but man i’m so far removed from using the latest. i’ve been bitten so many times by lazy devs who release backwards incompatible stuff.
i also think you can use reagent 1.7 and just manually insert the new libraries, but of course you’ll have to add the create-react-class compatibility library too
the cljs side didn’t change much. juho mostly just added stuff to work with fragments.
ideally I could just from my library that requires 16 do an :exclusions and use my older 15 react brough in by reagent, eh?
i mean, it’s a cljsjs package so theres a very low likelihood that you actually need the latest react.
yea if you are using cljsjs you have to do an exclusion and then include in manually. and hope that there’s a cljsjs release for react 16 😛
would be nice to have a cljs-focused tool like shadow that handles really common patterns like compile, hash, npm integration, etc. but if the repl isn’t at least on par with fighweel it’s a nonstarter, for me
i’d really just like to see his npm management and externs inference get incorporated. it is so much better.
it didnt offer history across sessions, if you executed a syntax error it would just quit the process, i couldnt figure out any way to get it to play with vim-fireplace
interesting. i mostly rely on hot reloading and the only thing i need the repl for is my ide
Are there any examples of how to use reagent with a react component from npm that is written in JSX? Preferably using the npm-deps option
@juhoteperi Double checked and yes it didn’t. Getting a bunch of errors though:
etc. Haven’t been using external libs outside of cljsjs in a while. So maybe it’s something obvious I’m missing
_meta.js:19 Uncaught ReferenceError: META is not defined Uncaught ReferenceError: es6Symbols$$module$Users$viktor$www$projects$pilloxa_log_analyzer$node_modules$babel_runtime$node_modules$core_js$library$modules$es6_symbol is not defined at es6.symbol.js:100 Uncaught TypeError: Cannot set property 'wrap' of undefined at runtime.js:8
my understanding is that if the lib uses JSX, the npm package contains a compiled bundle so you don't need babel or whatever to use it
One approach is the double bundle approach explained here: https://github.com/pesterhazy/presumably/blob/master/posts/double-bundle.md, also see https://github.com/pesterhazy/double-bundle
Warning: Use the `defaultValue` or `value` props on <select> instead of setting `selected` on <option>.
Ah, nevermind. I've used something inappropriate as a value. Neither number nor string.