Open garyb opened 8 years ago
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.
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.
Any update here? I just ran into this as well.
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.
No worries.
As raised in this comment: https://github.com/slamdata/purescript-affjax/pull/38#issuecomment-181652481