Developing Locally with Typekit,, and Browsersync

Recently I ran in to an interesting problem. When you initialize a new "kit" on typekit you are prompted to enter a list of domains that your kit will be allowed to function properly on. Typically you would enter the address of your live site (e.g. '') as well as an address for local testing (e.g. '' or 'localhost'). Neither of these options for local development worked for me. Managing a list of LAN addresses would be foolish (and probably impossible) on a large team where people are working from different locations. Simply stating localhost would prevent fonts from being previewed on other devices with a tool like BrowserSync, Ghostlab, or Adobe Edge Inspect which all rely on your computer's LAN address.

Typekit kit creation prompt

In my moment of need I turned to twitter and thankfully Chip Cullen answered my call:

Some of the developers at 37signals developed a custom DNS tool named to deal with similar problems. You can use xip to "trick" your browser in to thinking an address like or is All you have to do after this is add * to your typekit "kit" settings and you're good to go.

Typekit kit creation prompt


After solving this, I discovered I was running in to another problem: the suffix was interfering with live reloading in Browsersync (my preferred device syncing tool: fully featured, open source, *nix agnostic). Shane Osborne, the maintainer of Browsersync responded to my feature request very promptly and there is now an option to append whatever suffix you like to your IP address. Here is an example of adding the option to your gruntfile:

                hostnameSuffix: ""