Пропустить теорию и перейти прямо к задачам
Ссылка на учебник: http://learn.javascript.ru
Сразу расскажу про несколько особенностей яваскрипта, о которых может быть не написано (или мало написано) в учебниках, но которые стоит понимать:
| watchman watch-del-all && rm -rf node_modules/ && yarn cache clean && yarn install && yarn start -- --reset-cache |
| function PrivateRoute ({component: Component, authenticated, ...rest}) { | |
| return ( | |
| <Route | |
| {...rest} | |
| render={(props) => authenticated === true | |
| ? <Component {...props} /> | |
| : <Redirect to={{pathname: '/login', state: {from: props.location}}} />} | |
| /> | |
| ) | |
| } |
| const obj1 = {name:"xiaoming", age: 23} | |
| const obj2 = {age: 33} | |
| const obj3 = {...obj1, ...obj2} | |
| //obj3 ==> {"name":"xiaoming","age":33} |
Пропустить теорию и перейти прямо к задачам
Ссылка на учебник: http://learn.javascript.ru
Сразу расскажу про несколько особенностей яваскрипта, о которых может быть не написано (или мало написано) в учебниках, но которые стоит понимать:
| git branch -m old_branch new_branch # Rename branch locally | |
| git push origin :old_branch # Delete the old branch | |
| git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
#Error management in gulp
Sucking at something is the first step to becoming sorta good at something
No one can assure you, that plugins will run smooth in any circumstances (except for tests - they could), so neither should you convince anyone, that your plugin will never break. Only thing, that you could possibly do (if something gone wrong) - is gracefully inform your plugin user, that something went wrong and die.
We are will use this plugin from beginning to demonstrate error management. Suppose you have a task in gulpfile.js that contains this code (we modified it a little bit to be closer to real-usage):
var coffee = require('gulp-coffee');| ps aux | grep node | |
| kill -9 PID | |
| (Replace PID with the process Id of the Node) | |