Scaffold and build your projects way more faster than before. Preconfigured frontend devstack to the absolute perfection. Fully automated to save your precious time. Ready for any type of web project.
A little example project is here: manGoweb/mango-cli-example.
If you already have mango-cli
you can init the example project simply by mango init [your-directory]
Styles | |
---|---|
Stylus | expressive, robust, feature-rich CSS preprocessor |
Sass | CSS with superpowers |
Less | the dynamic stylesheet language |
Autoprefixer | vendor prefixes based on the real usage |
Clean-CSS | Fast and efficient CSS minifier |
Templates | |
Jade | robust, elegant and feature rich template engine |
Scripts | |
Babel | Use next generation JavaScript today |
React | JavaScript library for building user interfaces from Facebook |
CoffeeScript | little language that compiles into JavaScript |
Webmake | JavaScript bundling with require() in the browser |
UglifyJS | JavaScript minifier |
Tools | |
BrowserSync | Time-saving synchronised browser testing |
NPM | Node.js package manager |
Gulp | Automated build tasks |
Imagemin | Seamless image minification |
Sourcemaps | debug like a pro |
Install mango-cli once from npm
and use it everywhere:
npm install -g mango-cli
Just a few requirements you already have: Node.js and Git executable in PATH
and if you are running Windows, there are even some more special requirements because of node-gyp.
mango init
- scaffolding and initializationmango install
- dependency installationmango build
- production buildmango dev
- development mode
Feel free to use mango [command] -h
for detailed instructions
mango init [options] [directory]
Forks a template into folder.
Options:
-s, --source [git_repository]
- git repository with a template to fork. Default is currently the Frontbase
mango install [packages...]
Installs packages from NPM and stores them in node_modules
folder, from where you can require
them (thanks to browserify).
Maintain current list in the mango.yaml
config file under the dependencies
section.
Assuming the config file mango.yaml
is present in a current directory and contains:
styles:
- styles/screen.styl
scripts:
- scripts/index.js
images:
- images/**/*.{jpg,png,svg}
templates:
- templates/**/*.jade
static:
- fonts/**
dependencies:
- jquery
watch:
- app/**
dist_folder: dist
Config file can be also in mango.json
file and parsed as a JSON file.
mango build [tasks...]
All assets are compiled and minified into dist_folder
, ready for production use.
In case of server compilation try a stripped down mango-cli-core package instead.
Options:
[tasks...]
- run only specified tasks asstyles
,scripts
,images
,templates
,static
mango dev [http_proxy]
Starts BrowserSync server (or proxy server) and watch for assets change.
More in Configuration options docs...
Copyright 2016 by manGoweb s.r.o. Code released under the MIT license. Evolved from Frontbase devstack.