aritheelk / inferno-boilerplate

🔥 Inferno Boilerplate 🔥

Mission Statement

I personally have always been one who learns best by following examples and reverse engineering real world code. For that reason, I have constructed this boilerplate; in the hopes that anyone who is new to Inferno will be able to pick it up and not only have a valuable starting point, but actually be able to learn how to build useful applications using a real world stack.

Features

• Inferno
• Redux
• Custom CLI Utility
• Webpack
• Babel

Demo

 🔥 Click Here to View the Live Demo 🔥

Documentation

1. Setup & Installation
2. Running Development Server
3. Linting
4. Building

Notes

• inferno-boilerplate is in its early states; if you notice any bugs while using it, please open an issue!

License

Inferno Boilerplate is under the MIT License

inferno-boilerplate's Issues

Version Issue on npm install

Seems version problem, could give some pointer to the right solution.

npm WARN [email protected] requires a peer of webpack@1 || ^2.1.0-beta but none was installed.
npm WARN [email protected] requires a peer of webpack@^1.9.11 but none was installed.
npm WARN [email protected] requires a peer of webpack@1 || ^2.1.0-beta but none was installed.
npm WARN [email protected] requires a peer of node-sass@^3.4.2 but none was installed.
npm WARN [email protected] requires a peer of webpack@^1.12.6 || ^2.1.0-beta but none was installed.

TODO: implement flowtype support

In order to solidify this boilerplate and make it bulletproof, it needs support for type checking. Luckily this is something that can be progressively implemented, but the initial support for it needs setup before any files can begin implementing flowtype support.

Hit List:

Flowtype Setup

• Add flow to the project's dev dependencies
• Configure via .flowconfig

Components

• Button
• Header
• Input
• List
• MovieRow
• Nav
• Wrapper

Containers

• AboutPage
• HomePage

Templates

• component.test.js
• container.test.js

Uncaught TypeError: Cannot read property 'pathname' of undefined

Problem:
Error gets thrown in the browser on a search

How to reproduce:
yarn
yarn start
open localhost:4000 in chrome
search 'batman'
error output in chrome console

main.js:10502 Uncaught TypeError: Cannot read property 'pathname' of undefined
    at getURLString (main.js:10502)
    at match (main.js:11041)
    at RouterContext.render (main.js:11148)
    at RouterContext._updateComponent (main.js:6520)
    at patchComponent (main.js:3918)
    at patch (main.js:3733)
    at patchComponent (main.js:3945)
    at patch (main.js:3733)
    at patchComponent (main.js:3945)
    at patch (main.js:3733)

TODO: implement unit testing

This definitely needs a unit testing suite installed before recommending it's use in serious projects.

I'm currently leaning towards the ava test runner. However I remember hearing about issues with testing react projects on CI servers due to high number of individual test processes. If this is still an issue, it might be worth looking into other solutions.

Tests need written for individual components/containers as well as for the template component/container. This will aid in easy generation of component test files using the yarn mk comand.

Hit List:

Components

• Button
• Header
• Input
• List
• MovieRow
• Nav
• Wrapper

Containers

• AboutPage
• HomePage

Templates

• component.test.js
• container.test.js