handy-dev-tips

I'm creating this repo as a dumping ground for all the useful tips I've found and don't want to lose track of. These have all saved me a lot of time and grief.

###Finding All jQuery Events On an Element

Event-based views are a real pain when you don't know where your events are coming from. Here's how to see what jQuery events are triggering on any DOM element.

var domElem = $('body')[0];
$._data(domElem, 'events');
//domElem must be a true DOM element, not a jQuery object

Running WebStorm as your Git Diff/Merge Tool

WebStorm's diff tool is amazing, so using it for Git is a no-brainer. Just add the following to your %userprofile%.gitconfig file.

[merge]
	tool = webstorm
[mergetool "webstorm"]
	cmd = cmd.exe //c "\"webstorm\" merge \"$LOCAL\" \"$REMOTE\" \"$BASE\" \"$MERGED\""
	trustExitCode = true
[diff]
	tool = webstorm
[difftool "webstorm"]
	cmd = cmd.exe //c "\"webstorm\" diff \"$LOCAL\" \"$REMOTE\""

Targeting Older Version of NodeJS with ESLint

Many services (AWS, for instance) run older versions of Node, but often you don't want to cripple your local environment by running an outdated distribution. To keep yourself from delivering code to the service that isn't supported, use the following structure in your ESLint settings file.

{
  “plugins”: [“node”],
  “extends”: [“eslint:recommended”, “plugin:node/recommended”],
  “env”: {
    “node”: true
  },
  “rules”: {
    “node/no-unsupported-features”: [2, {“version”: 4}]
  }
}

##TFS

TFS is a bad source control system, compared to Git or SVN. There are a few things you can do to lessen the pain.

###Move Shelveset from Branch to Branch

Download the VS 2015 Power Tools here: https://visualstudiogallery.msdn.microsoft.com/898a828a-af00-42c6-bbb2-530dc7b8f2e1

From a directory inside your VS project, run the following command:

tfpt unshelve /migrate /source:"$/ProjectName/Branch" /target:"$/ProjectName/Targetbranch" "My Shelveset Name"

You'll get a couple of straightforward prompt windows. Resolve any conflicts and you'll end up back at the command prompt. You're done.

##Local Environment Setup

Setting Up NPM, Bower, Git and Python behind a corporate proxy

This is a real pain, and I can't say how many times I've had to look this up on stackoverflow. So, here it is for posterity.

####Git In your %userprofile%.gitconfig file:

[http]
	proxy = http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:80
[https]
	proxy = http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:443
[url "https://"]
	insteadOf = git://

Note that you'll have to replace anything in {{ }}. If you're not sure what your proxy address is, take a look in internet explorer under Settings >> Internet Options >> Connections tab >> LAN Settings. It should be there, or it should be loading a .pac file that you can download and view as a text file. Your proxy URL will be in there somewhere.

####NPM In your %userprofile%.bowerrc file:

{
	"proxy":"http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:80",
	"https-proxy": "http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:443",
	"registry": "http://bower.herokuapp.com",
	"directory":"./bower_components",
	"strict-ssl": false
}

####Bower In your %userprofile%.npmrc file:

proxy=http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:80/
https-proxy=http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:443/

####Python In your %userprofile%\AppData\Roaming\pip\pip.ini file, you'll need to add the following. You will need to create this file and its parent folder if they don't already exist.

[global]
	trusted-host = pypi.python.org
	proxy = http://{{username}}:{{proxy pw}}@{{mycorpproxy}}.com:80

wsrast/handy-dev-tips

handy-dev-tips

Running WebStorm as your Git Diff/Merge Tool

Targeting Older Version of NodeJS with ESLint

Setting Up NPM, Bower, Git and Python behind a corporate proxy