spdy issue

Hi,

The following:

const zetta = require('zetta')

zetta()
  .name('Test')
  .listen(1337, function () {
    console.log('Zetta is running')
  })

Fails beautifully with the following message:

> node index.js

util.js:972
    throw new TypeError('The super constructor to "inherits" must not ' +
    ^

TypeError: The super constructor to "inherits" must not be null or undefined
    at Object.exports.inherits (util.js:972:11)
    at Object.<anonymous> (/Users/marvin/Documents/Code/zetta/node_modules/spdy/lib/spdy/connection.js:86:6)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/marvin/Documents/Code/zetta/node_modules/spdy/lib/spdy.js:20:19)

I am on macOS on node 7.7.3.

[marvinroger]

And, simple workaround:

process.EventEmitter = require('events').EventEmitter

const zetta = require('zetta')

zetta()
  .name('Test')
  .listen(1337, function () {
    console.log('Zetta is running')
  })

[AdamMagaluk]

Hi Scott,

I agree with you on spdy, it’s been a nightmare and moving target trying to upgrade. I agree with your assessments on http/2 and i followed the Node.js API when it was being drafted and there were holes that zetta needed. But not sure what the state is I haven’t been active in that for 2 years. Its worth re-evaluating.

During the SPDY upgrade i was also working under the constraint that Zetta versions be backwards compatible from a network and protocol perspective. If we’re left with the option of making breaking changes and zetta being abandoned we could evaluate that contraint.

I’m always happy to advise and hop on a GVC and review PRs when I can. I agree with you and would love for Zetta to live on, I think it still has plenty of potential.