Try to find a workaround for browserify's node-compatible output

[garyb]

As raised in this comment: #38 (comment)

[ozanmakes]

Sorry for not following up on this. I failed to find a quick fix and since browserifying purescript code for a node.js module is an esoteric use case I went with a fork instead.

[garyb]

Ok great, thanks for the update. I'll still see if I can try to fix it at some point, as it's relying on a slightly dubious workaround at the moment.

[joneshf]

Any update here? I just ran into this as well.

[garyb]

Sorry, I never looked into it any further. It was long enough ago that I don't even remember the ins and outs of the current hack.

[joneshf]

No worries.