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^

is this a safe upgrade? who knows, the js world is spooky.

I think the latest reagent snapshot uses react 16

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

actually I think it is in pretty good shape

the cljs side didn’t change much. juho mostly just added stuff to work with fragments.

but at any rate, I do think that old reagent will work with react 16

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.

that’s a bad idea too, lol.

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 😛

this is why i use shadow 🙂

i gave shadow a try, the repl is just no bueno and that’s where i do 50% of my work

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

what didn’t you like? the editing?

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

And boot

@vikeri npm packages don't usually contain JSX code

@juhoteperi Double checked and yes it didn’t. Getting a bunch of errors though:

_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

This should work but it's not particularly elegant

I'm getting this message when trying to use <select> in reagent

Warning: Use the `defaultValue` or `value` props on <select> instead of setting `selected` on <option>.

But when I add value to a <select> reagent sends another warning

Warning: Failed prop type: Invalid prop `value` supplied to `Select`.

Ah, nevermind. I've used something inappropriate as a value. Neither number nor string.

@vikeri what package are you trying to include? my guess is that you have failed to include a transitive dependency