Decrease file size

[jhnns]

This PR introduces a trie-based approach instead of a big regular expression. The trie is built upon npm install using the postinstall hook. If something goes wrong, the postinstall script falls back to a list that has been compiled on prepublish.

Using the trie-based approach, I was able to reduce the parse size from 216 KB to 63 KB. The compressed size went down from 71 KB to 30 KB. And the best thing about it: it's even not a breaking change 😁.

[vshulev]

@jhnns I believe this is causing installation to fail when running npm i -g parse-domain inside the Node Docker image. Tested this on images 8.9 and 8.11 and getting the same result:

+ npm i -g parse-domain

> parse-domain@2.1.1 postinstall /usr/local/lib/node_modules/parse-domain
> node scripts/build-tries.js

Downloading public suffix list from https://publicsuffix.org/list/public_suffix_list.dat... ok
Writing /usr/local/lib/node_modules/parse-domain/build/tries/current/icann.complete.json... 
Could not update list of known top-level domains for parse-domain because of EACCES: permission denied, mkdir '/usr/local/lib/node_modules/parse-domain/build/tries/current'
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! parse-domain@2.1.1 postinstall: `node scripts/build-tries.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the parse-domain@2.1.1 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-06-01T14_32_15_916Z-debug.log

I was originally trying to run npm i -g semantic-release conventional-changelog-eslint - one of these two packages contains parse-domain as a dependency (not sure which one). However directly installing parse-domain produces the same error.

[jhnns]

@vshulev thanks for letting me know 👍. Let's continue the discussion at #35