fix(#6): use manual fs shim

[petermikitsh]

@andreinitescu

Instead of relying on browserify and transform-loader, I've added a manual fs shim.

This is technically less correct since we are losing the file contents. For example, here's a diff of node_modules/fontkit/index.js:6878 (after running through webpack):

- var trie = new UnicodeTrie(Buffer("AAH.......8KmzQDjmuTAQ==","base64"));
+ var trie = new UnicodeTrie(__webpack_require__(/*! fs */ "./docs/fsShim.js").readFileSync(__dirname + '/data.trie'));

Before:

After:

So the runtime behavior is changing, but it practically doesn't impact any of the ligature APIs. This change only applies to the docs site, and not the ligatures npm library.

[andreinitescu]

It works 👌
Do you know if this fs mock shim has any impact on rendering the glyphs with fontkit ?
I'm talking about using this API
glyph.render(ctx, size) https://github.com/foliojs/fontkit#glyphrenderctx-size
My tool also needs to draw the ligatures/glyphs.

Thanks again for your help

[petermikitsh]

I don't think this will impact rendering with fontkit, though this project doesn't use that fontkit feature.

You might be able to explore using the browser to natively render the glyphs. https://developer.mozilla.org/en-US/docs/Web/CSS/font-feature-settings

Example usage here:

ligatures/docs/index.js

Line 32 in 35d5fbe

font-feature-settings: "liga", "dlig", "calt", "ordn", "rlig";