monotony
lack of variety and interest; tedious repetition and routine. (which is how I feel everytime I make a new react webpack build).
- babel
- react
- redux
- thunk
- express
- webpack
- server side rendering
- chunking
- dependancies
React with Redux, ran by Express, multi-target built by Webpack with Babel, dependency solution for client and server-side rendering.
CSS modules, code splitting, hydration, other buzz words.
why?
I prefer stitching together libraries to do what I need vs a framework, it's more fun. But alas, I put together my very opinionated "framework" to decouple my build and scoffolding to an external project to be re used.
Better documentation, linting, and other stuff, and cleanup, and I use this for personal.
Any feedback/recommendations is greatly appreciated.
your documentation is super poor, spoon feed me the project setup...
K, clone this repo, fish around, use it as yours, enjoy
basic usage:
npm install monotony --save
- create files (these files are ran through babel, look at
/examples/
dir)
monotony.config.js
return the name
, routes
, and reducers
routes.js
that follows the Route Configuration Shapemonotony.client.js
import Client
, pass in the config, and start er upmonotony.server.js
import Server
, pass in the config, attach anything you want to app
(express)
package.json
, add start
and build
scripts:
"start": "monotony start",
"build": "monotony build"
npm run start
to spin up your local, hit localhost:9090 and profit