jthrilly

function FindProxyForURL(url, host)
{
    if (shExpMatch(url, "*.bbc.co.uk/iplayer*")
     || shExpMatch(url, "*.bbc.co.uk/mediaselector*")
     || shExpMatch(url, "zaphod-live.bbc.co.uk.edgesuite.net/*")
     || shExpMatch(url, "bbcfmhds.vo.llnwd.net/*"))
    {
        return "SOCKS 127.0.0.1:1055";
    }
    else

jthrilly

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

jthrilly

{
  "name": "gsap-to-video",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "fs-extra": "^7.0.0",
    "puppeteer": "^1.7.0"
  }
}