Grunt helps front-end web developers automate common tasks such as: linting, testing, sass compilation, watching assets. Check basic features of node.js, npm and Grunt.
2. About Pagepro:
• Internet Software House from Poland
• Operating since 2010
• Clients from Western Europe and U.S.
• 176 projects done in 2014
• 1758 PSDs converted into
HTML5 in 2014
3. Common Front-end tasks
• Compile SASS / LESS
• Minify
• Uglyfi
• Test
• Optimize
• Analyze
• Modules & Dependencies
10. node.js
Traditional I/O
var result = db.query('select x from table_Y');
doSomethingWith(result); //wait for result!
doSomethingWithOutResult(); //execution is blocked
11. node.js
Non-blocking I/O
db.query('select x from table_Y', function (result) {
doSomethingWith(result); //wait for result!
});
doSomethingWithOutResult(); //executes without any delay!
25. When not to use node.js?
• When you are doing heavy and
CPU intensive calculations on
server side, because event-loops
are CPU hungry
• Node.js API is still in beta, it keeps
on changing a lot from one revision
to another and there is a very little
backward compatibility. Most of the
packages are also unstable.
Therefore is not yet production
ready.
26.
27. GRUNT
• Lint
• Test
• Compile
• Open browser
• Run browser
• Watch assets
• Recompile
• Reload browser
36. GRUNT
It’s a core concept of Grunt. When
we create a task, we add targets to
it.
Every target represents a set of
actions and files the task will be
run over.
We can run a task’s target by simply
appending it to the task name.
grunt mytask:mytarget