Closed 9point6 closed 10 years ago
It was originally designed to work in browsers (comes w/ some shims, lazy loading data selectively...). For NodeJS some assumptions might change but overall I don't think there's a concrete reason to not bundle NodeJS transport layer in (other than having to put in browser vs server check & whatnot).
Feel free to submit a PR, unless @mde has other thoughts?
see pull request above.
look good?
tests please :)?
Ah, merged already!
I wrote a test, anyway.
Let's get that test in there!
yeah I made a commit on top of @9point6's commit to test it, but the more tests the better :)
Is there any reason why the built in transport doesn't include a case for if the library is running on node JS (defaulting to something like the function used in the tests)?
I realise it's trivial to override the function, but it seems odd to require that kind of boilerplate if a developer wants to use the library in a node project