.node yields incomplete JSON objects

[volkanunsal]

Recently, the node method has been returning non-JSON strings to the callback function and I can't figure out why. This used to work before. My function looks like this:

oboe(this.options.url)
      .node('features.*', (f) => {
      });

The JSON object from the server looks like this:

{
 "type": "FeatureCollection",
  "features": [
    {"id": 1}, {"id": 2}, {"id": 3}
  ]
}

The first time it returns a correct object. But the second and third time this function is called, the results are malformed. Any idea what might be going on?

[volkanunsal]

I am also observing that occasionally there are errors like this:

Uncaught TypeError: Cannot read property '0' of undefined ./~/oboe/dist/oboe-browser.js:122 

Looks like it's coming from here.

[JuanCaicedo]

@volkanunsal could you try this using the function keyword instead of ES6's fat arrows? My suspicion is that since you are able to work with this inside the node callback, the Oboe code also uses this. Using the fat arrow changes the binding on this, which changes it for all the later instances.

Just a hunch though, hopefully we can verify if that's the case!

[tmkujala]

I've also started seeing the same TypeError when running under node:

TypeError: Cannot read property '0' of undefined
    at /app/node_modules/oboe/dist/oboe-node.js:121:33

Any idea what the root issue is here?