CelticParser

// Node.js CheatSheet.
// Download the Node.js source code or a pre-built installer for your platform, and start developing today.
// Download: http://nodejs.org/download/
// More: http://nodejs.org/api/all.html


// 0. Synopsis.
// http://nodejs.org/api/synopsis.html

CelticParser

task_security() {

  # Reference: http://blog.nodesecurity.io/2014/02/01/new-feature-validate-modules-with-npm-shrinkwrap

  if [ ! -f 'npm-shrinkwrap.json' ]; then
  
    echo -e "\n\e[40mAudit: \e[101m[FAIL]\e[0;49;93;1m Create npm-shrinkwrap.json by running: \e[0m\n
      $ npmflat --production\n"
    exit 1;
  fi

CelticParser

var pjason = require('./package.json');
console.log(pjson.name);

CelticParser

How to Update a GitHub Forked Repository

In your local clone of your forked repository, you can add the original GitHub repository as a "remote". ("Remotes" are like nicknames for the URLs of repositories - origin is one, for example.) Then you can fetch all the branches from that upstream repository, and rebase your work to continue working on the upstream version. In terms of commands that might look like:

# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches,

CelticParser

language: node_js
node_js:
  - "0.10"
  - "0.12"
  - "iojs"

CelticParser

node_modules
test
.c9

CelticParser

{
  "undef": false,
  "esnext": true,
  "laxbreak": true,
  "laxcomma": true,
  "indent": 2
}

CelticParser

node_modules
npm-debug.log
.c9

CelticParser

# Ignore un-needed files and directories for export of production releases
# See: http://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#Exporting-Your-Repository

test/ export-ignore
.gitattributes export-ignore
.gitignore export-ignore
.jshintrc export-ignore
.npmignore export-ignore
.npm-debug.log export-ignore
.travis.yml export-ignore