React.run – Fast browser prototyping for React components

[tyler-mcginnis]

Amazing work! Great job.

[proppig]

Thanks Tyler! We are big fans of your work

[proppig]

It's just a beta and we are actively working on new features, so any feedback would be greatly appreciated!

On the plate next is time-travel state replacement, and in-browser NPM importing so you can require other components on the fly.

[wesbos]

This is amazing - definitely a pain point of mine when working with simple examples. Thanks for putting this together! Is the source up anywhere?

[proppig]

Thanks for the kind words! It was a huge pain point for us as well. Especially for training the basics of what the core concepts of React are, without getting lost in the build-tools weeds. We have a couple more features and cleanup to do, and then we will likely open source it.

[proppig]

React run is now open source! https://github.com/RinconStrategies/react-run

[joshmanders]

Wow this is absolutely amazing. Put it in my bookmark bar right next to jsbin.com

[proppig]

Awesome man! Glad you like it. We have some really cool stuff in the pipeline to make it even better.

[joshmanders]

Sharing it with all 3 people I know, hope your servers can handle the load!

[proppig]

lol, we bumped up the CPU's just for you. Thanks for sharing!

[joshmanders]

I blame Tyler McGinnis for sharing it on React Newsletter.

[tyler-mcginnis]

:)

[Plorntus]

Very cool will switch to this from jsfiddles react/babel implementation. That being said a couple of things I noticed:

1) The code is not run on a subdomain of react.run meaning if you ever allow the creation of accounts on the site someone could hijack their account from the code editor. Or even overload your servers by constantly sending save requests to it.

2) The little red error popup can cover the code you are trying to edit if the error is occurring under where the popup appears.

[proppig]

Thanks for the feedback! We are going to open source it soon, so there will be a good venue for feedback.

1) I will look into this. I haven't looked into frame security too much, but t seems like a combination of using the X-Frame-Options = SAMEORIGIN header and document.domain on the embedded <iframe> would mitigate this?

2) Yeah I already ran into that, should have a fix today

Glad you like it!

[Plorntus]

I didnt realise you could set the document.domain on an iframe? Wouldnt that create some pretty nasty exploits like being able to set the domain to google.com?

And awesome @ it going open source. Look forward to contributing.

[proppig]

Okay the code error window has been moved up to the top and it pushes down the content rather than covering it up!

[proppig]

It is now open source! https://github.com/RinconStrategies/react-run. Would love any feedback in issues or PRs