<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>React on Justin Carmony</title>
		<link>https://www.justincarmony.com/tags/react/</link>
		<description>Recent content in React on Justin Carmony</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 03 Oct 2015 20:00:46 +0000</lastBuildDate>
		
			<atom:link href="https://www.justincarmony.com/tags/react/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Talk: Writing Interactive User Interfaces with PHP &amp; React.js - PHPNW15</title>
				<link>https://www.justincarmony.com/2015/10/03/talk-writing-interactive-user-interfaces-with-php-react-js-phpnw15/</link>
				<pubDate>Sat, 03 Oct 2015 20:00:46 +0000</pubDate>
				<guid>https://www.justincarmony.com/2015/10/03/talk-writing-interactive-user-interfaces-with-php-react-js-phpnw15/</guid>
				<description>&lt;p&gt;Wow, this talk. I had warned myself when I started speaking I would never, ever be one of those speakers who came ill-prepared and bombed a talk. It took being ~30 talks in my speaking career where I let my guard down, and at one of my very favorite conferences, I blew it. (Ok, maybe not bombed it, but I didn&amp;rsquo;t do well to my standards)&lt;/p&gt;&#xA;&lt;p&gt;Ok, I didn&amp;rsquo;t totally blow it, but if you watch the video (I was almost tempted not to post it) feel free to skip the live demo. What happened is my first part of my talk went incredibly fast, and then I ran into technical difficulties with my live demo (which I didn&amp;rsquo;t prepare or harden very well in advance). What was the worst part is because I took so long trying to get my live demo to work, I had well-prepared content I had to rush.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Talk: Writing Interactive User Interfaces with PHP &amp; React.js - Utah PHP Usergroup</title>
				<link>https://www.justincarmony.com/2015/07/16/talk-writing-interactive-user-interfaces-with-php-react-js-utah-php-usergroup/</link>
				<pubDate>Thu, 16 Jul 2015 20:00:24 +0000</pubDate>
				<guid>https://www.justincarmony.com/2015/07/16/talk-writing-interactive-user-interfaces-with-php-react-js-utah-php-usergroup/</guid>
				<description>&lt;p&gt;This was my dry-run for my upcoming talk at PHP North West 2015. Check out that talk for the final copy of the slides.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Webpack, React, and Multiple Versions Issues</title>
				<link>https://www.justincarmony.com/2015/04/02/webpack-react-and-multiple-versions-issues/</link>
				<pubDate>Thu, 02 Apr 2015 18:10:21 +0000</pubDate>
				<guid>https://www.justincarmony.com/2015/04/02/webpack-react-and-multiple-versions-issues/</guid>
				<description>&lt;p&gt;I’ve been using React successfully for several projects, and tonight I ran into a problem I hadn’t experienced before. I was trying both &lt;a href=&#34;https://www.npmjs.com/package/react-d3&#34;&gt;&lt;code&gt;react-d3&lt;/code&gt;&lt;/a&gt;and &lt;a href=&#34;https://www.npmjs.com/package/react-d3-components&#34;&gt;&lt;code&gt;react-d3-components&lt;/code&gt;&lt;/a&gt; when I would get an error on rendering:&lt;/p&gt;&#xA;&lt;p&gt;&lt;code&gt;Uncaught TypeError: Can&#39;t add property context, object is not extensible&lt;/code&gt;&lt;/p&gt;&#xA;&lt;p&gt;This error had a very, very deep stack trace far into the depths of React, and I was worried I had encountered a nasty React bug. After some poking around &amp;amp; googling, I discovered that multiple versions of React do not play nicely with each other, at all. When I had installed both those react component libraries, each installed their own version of React, version 0.12. I was using React version 0.13.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Barebones Example of using React &amp; Webpack</title>
				<link>https://www.justincarmony.com/2015/03/19/barebones-example-of-using-react-webpack/</link>
				<pubDate>Thu, 19 Mar 2015 18:13:35 +0000</pubDate>
				<guid>https://www.justincarmony.com/2015/03/19/barebones-example-of-using-react-webpack/</guid>
				<description>&lt;p&gt;The biggest hurdle to starting with &lt;a href=&#34;http://facebook.github.io/react/&#34;&gt;React&lt;/a&gt; is getting your JSX files to compile to plain JavaScript. My preference is to use &lt;a href=&#34;http://webpack.github.io/&#34;&gt;webpack&lt;/a&gt; to accomplish this.&lt;/p&gt;&#xA;&lt;p&gt;If you go and google “react webpack starter” you get some great, fully featured starters like &lt;a href=&#34;https://github.com/webpack/react-starter&#34;&gt;react-starter&lt;/a&gt;. The problem is if you’re not starting from scratch, it can be very hard to see what files / settings / etc you need to bring into your project to make it work.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Thoughts on Learning React &amp; Flux</title>
				<link>https://www.justincarmony.com/2015/03/18/thoughts-on-learning-react-flux/</link>
				<pubDate>Wed, 18 Mar 2015 18:15:25 +0000</pubDate>
				<guid>https://www.justincarmony.com/2015/03/18/thoughts-on-learning-react-flux/</guid>
				<description>&lt;p&gt;I started to write a blog post detailing everything I’ve learned over the last few months building applications with &lt;a href=&#34;http://facebook.github.io/react/&#34;&gt;React&lt;/a&gt; &amp;amp; &lt;a href=&#34;https://facebook.github.io/flux/&#34;&gt;Flux&lt;/a&gt;. After writing down about 10% of it, I realized it was becoming far too long. So, instead, I’ll be doing a series of posts over the next few weeks.&lt;/p&gt;&#xA;&lt;p&gt;Over the last two months, interest in React has had a surge of interest. If you look at the search term &lt;code&gt;reactjs&lt;/code&gt; &lt;a href=&#34;https://www.google.com/trends/explore#q=reactjs&amp;amp;date=today%2012-m&amp;amp;cmpt=q&amp;amp;tz=&#34;&gt;over the last 12 months&lt;/a&gt;:&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
