Skip to main content

Learning React: Part 1

I recently decided to start learning React for a new project at my employer. I’m going to try to post some of my findings along the way with the hopes that someone will find them useful. First, starting with a good up to date template is important. Things move so fast at the bleeding edge, a template can die in just a couple months. I wanted something integrated with SailsJS since I recently learned that, liked it, and needed a simple back-end for this new project. Despite how long Sails has been out, there doesn’t seem to be an up to date generator/template for Sails + React.

Side note, a fellow developer recommended react-hot-boilerplate to start with. It doesn’t come with a server back-end like Sails but it does appear to be better maintained than the other templates.

I started messing around with sails-generate-reactjs. Starting out, I really liked it. However, the repository has not been updated for about 3 months now and the author does not seem to be active on it any longer. Thus, it’s already outdated, such as its use of the deprecated grunt-react package. This initially didn’t give me too many issues on a side project using it in a Linux environment on Nitrous.io, however I started having transpiling issues on Windows at work.

Those weren’t too hard to mitigate though. I simply installed babelify and modified the “transform” option in “tasks/config/browserify.js” from
transform: [require('grunt-react').browserify]” to transform: [require('babelify')]

Modifying more to “require(‘babelify’).configure({stage:0})” permits all supported ES6/7 features in Babel. Beyond that though, I can now also switch to using the somewhat cleaner (IMO) module syntax such as “import React from ‘react’;” instead of “var React = require(‘react’);”.

I’m still having some issues with the asset pipeline not running as expected but I hope to clean those up soon.

Comments

Popular posts from this blog

Fancy FTP Deployment with Grunt

I recently dove into Grunt.js at work for automating our build process and I haven’t looked back. It’s an awesome tool with a plug-in for just about anything. I expected the usual would be there like JavaScript minification and concatenation, but I was surprised at a few others that I found, one being for FTP file deployment. Just shows how popular and community supported Grunt is.

There are a few FTP plug-ins available for Grunt. I didn’t do an analysis of all of them but ran across grunt-ftp-push which seemed to do what I needed so I decided to try it out. A simple ftp-push setup to upload an entire project via FTP could look like this:

grunt.initConfig({ftp_push:{all:{options:{host:'example.com',port:21,dest:'/project/path/',username:'user',password:'pass'},expand:true,cwd:'dist',src:['**/*','!**/*.zip']}}});
Some details here: I opted to put the username and password in the main config rather than using an .ftpauth file. The …

Accessing other HTTP servers on Cloud 9 IDE

If you're using Cloud 9 to do development, you'll quickly realize that only ports 8080 through 8082 are available to the outside world from your development box. This is generally not an issue as you can set your application to bind to the $PORT environment variable when in development mode. However, there are sometimes other servers that we want to make use of that host on different default ports.

I recently had to setup a Neo4j server which defaults the admin interface of port 7474. Unfortunately, I could not access the admin interface even through the IDE based web browser window. So, what to do? I could change the default server settings so that it runs on a different port. However, the app I'm working on with a team has 7474 hard-coded and I currently don't feel like writing a local only work-around.

After some searching, I ran across a neat Linux tool called socat. This allows us to easily forward one port to another. After a quick install via apt-get, I ran the …

Moving to Babel 6 on the Server

Cross post from my employer's development blog: http://rootinc.github.io/2016/03/14/babel-6-server/

Decided it was time to upgrade my server-side code to run on Babel 6. Below is a synopsis of all the issues I ran into and resolved while upgrading my 0.11.3 SailsJS server to run with Babel 6 transpilation.

The upgrade to Babel 6 itself is easily achieved in Sails by upgrading the `sails-hook-babel` package.

### Missing preset
`couldn't find preset "stage-0" relative to directory`
Just because a preset is on the official Babel preset page, doesn’t mean that Babel comes with it. Simple fix by installing the [package][1] from npm. Read more [here][2].
[1]: https://www.npmjs.com/package/babel-preset-stage-0
[2]: http://jamesknelson.com/the-six-things-you-need-to-know-about-babel-6/

### Need strict mode everywhere
`Block-scoped declarations (let, const, function, class) not yet supported outside strict mode`
I didn’t have to worry about this before, and I don’t feel like …