Closed nolanlawson closed 8 years ago
The differences between node and browser can probably be explained by (one of) the process.browser if-statements.
It's the _serializeValue
in abstract-leveldown
AFAICT, yeah.
In the browser, those two tests pass but the ones that fail also fail in abstract-leveldown
itself. Unfortunately when I fix them in abstract-leveldown
, I run into a browserify error. 😭
Fixed the browser/abstract-leveldown issue (https://github.com/Level/abstract-leveldown/pull/93), but this is still unresolved. Haven't figured it out yet.
If anybody wants to contribute the fix for this issue, it's pretty easy to reproduce:
npm it
Alternatively, you can npm run test-browser-local
and see the failures live in Zuul using your browser. Unfortunately the tests don't fail in the browser, probably due to a process.browser
switch somewhere as stated above.
created a pull request on abstract-leveldown, that should fix the problem. https://github.com/Level/abstract-leveldown/pull/96
tests are all green after the change
Pinning the version of abstract-leveldown to 2.4.1 also fixes the issue, which I'm perfectly fine with for now.
fixed in #51
Looks like a change in abstract-leveldown broke us:
I'm having a heck of a time testing this because it doesn't reproduce in the browser, and entirely different tests are broken in the browser for abstract-leveldown.