| echo 'export PATH=$HOME/local/bin:$PATH' >> ~/.bashrc | |
| . ~/.bashrc | |
| mkdir ~/local | |
| mkdir ~/node-latest-install | |
| cd ~/node-latest-install | |
| curl http://nodejs.org/dist/node-latest.tar.gz | tar xz --strip-components=1 | |
| ./configure --prefix=~/local | |
| make install # ok, fine, this step probably takes more than 30 seconds... | |
| curl https://www.npmjs.org/install.sh | sh |
| URL="https://raw.githubusercontent.com/git/git/master/contrib/completion/git-completion.bash" | |
| PROFILE="$HOME/.profile" | |
| echo "Downloading git-completion..." | |
| if ! curl "$URL" --silent --output "$HOME/.git-completion.bash"; then | |
| echo "ERROR: Couldn't download completion script. Make sure you have a working internet connection." && exit 1 | |
| fi |
| <!doctype html> | |
| <!-- http://taylor.fausak.me/2015/01/27/ios-8-web-apps/ --> | |
| <html> | |
| <head> | |
| <title>iOS 8 web app</title> | |
| <!-- CONFIGURATION --> |
Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.
If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.
| netstat -lptan | |
| netstat -lptu | |
| netstat -lptun | |
| # -l listen | |
| # -p process name | |
| # -t tcp | |
| # -a established connections | |
| # -n numeric addresses | |
| # -u udp |
| /** | |
| * Fetch data from the web and save it into a Google Sheet document | |
| * | |
| * Requirements: | |
| 1. NodeJS | |
| 2. npm install request | |
| 3. npm install cheerio | |
| 4. npm install edit-google-spreadsheet | |
| * Author: Ido Green | plus.google.com/+Greenido |
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
| // === Arrays | |
| var [a, b] = [1, 2]; | |
| console.log(a, b); | |
| //=> 1 2 | |
| // Use from functions, only select from pattern | |
| var foo = () => [1, 2, 3]; |
(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.