See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
#!/bin/bash | |
# Download GitKraken | |
wget https://release.gitkraken.com/linux/gitkraken-amd64.tar.gz | |
# copy the downloaded file into /opt directory | |
cp gitkraken-amd64.tar.gz /opt/ | |
cd /opt |
Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward
discussions repo
The final result: require() any module on npm in your browser console with browserify
This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.
Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
# Sync fork with original repository | |
# | |
# Requires an "upstream" remote, pointing to original repo | |
# e.g. `git remote add upstream [email protected]:user/repo.git` | |
alias git-sync-fork="git fetch upstream; git checkout master; git merge upstream/master" |
#!/usr/bin/env bash | |
# Setup script for hacking chrome devtools | |
# Source -> https://medium.com/p/8c8896f5cef3 | |
echo "Creating folder and initialize a git repo" | |
mkdir devtools-frontend && cd devtools-frontend | |
git init | |
echo "Adding chromium remote and initialize sparse checkout" | |
git remote add upstream https://chromium.googlesource.com/chromium/blink |