user socket.io server configuration

[incompl]

No description provided.

[jugglinmike]

Users may be setting the logLevel option today, making this a breaking change. If you want to keep the same major version for the next release, you should write:

// Maintain `logLevel` option for backwards compatibility.
// TODO: Remove this in next major release
if ('logLevel' in config) {
  if ('log level' in ioConfig) {
    throw new Error(
      'Socket.io logging level over-specified. Use config.logLevel ' +
      'or config["socket.io"]["log level"] (not both)'
    );
  }
  ioConfig['log level'] = config.logLevel;
}

[incompl]

I'm OK with the breaking change, I follow the practice of using minor version numbers for breaking changes if the major version number is zero (since it doesn't make sense to release a 1.0.0 for this)

[jugglinmike]

This is probably obvious from my review, but my advice would be

• Accept the few additional lines of cruft in favor of supporting your existing users
• Or:
  • If you have specific plans for additional breaking changes, document them in a "version 1.0 roadmap".
  • Otherwise, release 1.0 . A pre-1.0 library (especially one maintained in this way) is not attractive for live deployment.