hi good morning, I'm having a error with reagent 8 alpha2 Uncaught ReferenceError: process is not defined

Do you use :npm-deps?

ys

:compiler     {:main                 gecko.core
                    :output-to            "resources/public/js/compiled/app.js"
                    :output-dir           "resources/public/js/compiled/out"
                    :asset-path           "/js/compiled/out"
                    :npm-deps
                    {:react "16.0.0"
                     :react-dom "16.0.0"
                     :create-react-class "15.6.2"}
                    :install-deps true
                    :infer-externs true
                    :source-map-timestamp true
                    :closure-defines {goog.DEBUG true}
                    :preloads             [devtools.preload
                                           re-frisk.preload]
                    :external-config      {:devtools/config {:features-to-install :all}}
                    }

I was having the exact same problem a couple of days ago. Remove re-frisk.preload.

Refer to https://dev.clojure.org/jira/browse/CLJS-2393 for more details

trying it out! many thanks!

Uncaught Error: Undefined nameToPath for cljsjs.react

new error 🙂

Try lein clean, rm node_modules and run the build again.

By the way, if you won't add anything else to :npm-deps and React 15 is enough for you, you don't need :npm-deps at all.

well the problem is that I want also to run this via nodeJS

to perform some server-side render

Ah, I see.

the problem remains 😕

:infer-externs true

this is correct?

trying without

now

I've never used this flag - I use oops for JS interop.

Also, could you try the version of React that Reagent uses?

oops?

https://github.com/binaryage/cljs-oops

react 15.6.2

you could try putting that on top of your index.html

<script>window.process = window.process || {env: {NODE_ENV: "dev"}};</script>

not saying this is a proper solution but it may get you a step further 🙂

But only if everything else fails.

[reagent "0.8.0-alpha2" :exclusions [[cljsjs/create-react-class]
                                                      [cljsjs/react-dom-server]
                                                      [cljsjs/react-dom]
                                                      [cljsjs/react]]]

tried removing exclusions and seems to work

but seems odd

Aha! I did not have these exclusions in the first place.

In the migration guide to Reagent 0.8 it's stated that if React is found in node_modules, cljsjs/react will still be used, but only for externs. I'm not sure how that works, but maybe that's the problem.

yep

working in the browser testing with nodejs now

seems to be working

lost re-frisk only 🙂

thanks guys

You can still use it, but not in the preloads.

can you point me to how?

(enable-re-frisk-remote!)

something like this on my code?

Just call it in your :main, yes.

Just make sure that re-frisk is available as a dependency in the relevant build.

yep thanks

@brunex In #clojurescript it was pointed out that you can just add process.env as the first preload and leave re-frisk in the list of preloads.

going to give it a try

what is the best way to get a reagent component rendered as HTML

in reagent 8

Not sure if has been mentioned here yet (don’t see it), but some reason that I have not tracked down, the “BMI calculator” on this reagent tutorial page http://reagent-project.github.io/ isn’t working

the sliders don’t change the values of the height/weight/bmi

running the code it shows there locally works though. I believe it used to work on the site too (if I remember correctly). Someone who was just trying to learn reagent pointed this out to me yesterday because they were confused what it was supposed to be doing.

CC @juhoteperi

TypeError: Cannot read property 'renderToString' of undefined
    at reagent$dom$server$render_to_string

allways getting this error when trying to render stuff 😕

hi! how to add a custom HTML attribute to a reagent component?

Sounds very possible, thanks @mikerod for pointing that out!

No problem

For some reason Range inputs don't trigger onChange events

>For some reason Range inputs don’t trigger onChange events uh oh

... on this particular environment and adv build

Demo site is for now built using UMD module, I'll create issue about this and hopefully I can create tests to validate this case

Hi there. Is it possible to use Reagent component from JavaScript/React app?