Node compatibility issues?

[nicholaschantcs]

Does this store have compatibility issues because I saw the latest pull request is using nvm 0.10.40 and I tried to implement this module but it seems to be failing.

I am trying to achieve multi-tenancy using this plugin with seneca.make and seneca.save like it's being used with mongo-store.

I tested the module with node v4.2.4 , npm 3.7.3.

$ npm test

> [email protected] test C:\Users\chann\Desktop\seneca-elasticsearch
> mocha test --reporter spec

(node) child_process: options.customFds option is deprecated. Use options.stdio instead.
2016-02-29T14:06:16.980Z tbphtlz4iais/1456754776965/9312/- INFO hello   Seneca/0.6.4/tbphtlz4iais/1456754776965/9312/-
2016-02-29T14:06:17.204Z tbphtlz4iais/1456754776965/9312/- FATAL        plugin  search          sys     seneca  0.6.4   tbphtlz4iais/1456754776965/9312/-               Maximum call stack size exceeded            all-errors-fatal
...
...
...
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:399:20)
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:399:20)
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:399:20)
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:399:20)
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Function.EventEmitter.listenerCount (events.js:399:20)
    at Log.listenerCount (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:68:25)
    at Log.info (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\log.js:240:12)
    at ConnectionPool.addConnection (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\connection_pool.js:276:14)
    at ConnectionPool.setHosts (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\connection_pool.js:321:12)
    at new Transport (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\transport.js:71:25)
    at Object.EsApiClient (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\client.js:57:22)
    at new Client (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\elasticsearch\src\lib\client.js:101:10)
    at Suite.<anonymous> (C:\Users\chann\Desktop\seneca-elasticsearch\test\00entities.js:42:18)
    at context.describe.context.context (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\mocha\lib\interfaces\bdd.js:74:10)
    at Object.<anonymous> (C:\Users\chann\Desktop\seneca-elasticsearch\test\00entities.js:39:1)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\mocha\lib\mocha.js:172:27
    at Array.forEach (native)
    at Mocha.loadFiles (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\mocha\lib\mocha.js:169:14)
    at Mocha.run (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\mocha\lib\mocha.js:356:31)
    at Object.<anonymous> (C:\Users\chann\Desktop\seneca-elasticsearch\node_modules\mocha\bin\_mocha:366:16)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:313:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:136:18)
    at node.js:963:3
npm ERR! Test failed.  See above for more details.

Any suggestions would be good.

[AdrianRossouw]

confirmed, but it seems to be from one of the dependencies.

i'll check if the errors go away once i bump those.