David Pfeffer

I can't do that because `nvs auto on` clobbers the prompt: See this copy/paste from my console when I run it: ``` bytenik@BYTENIK-PC  D:\..\..\platform-ws   dev ≣ ...

Didn't see this when I made my issue (#875). I'm happy to attempt to implement this, but I do need a bit of guidance as to where to start in...

Since both interfaces and type declarations don't exist at runtime, decorators aren't allowed on them. As a result, I think the only option would be jsdoc on the union type...

Yes, making it promise-based would be ideal!

Incorporating #3661, #3660, and #3659 into this issue.

I've worked around some of these issues in a really hacky way by making a factory for the adapter class and then firing callbacks on arguments passed into the factory,...

@darrachequesne Awesome, that looks great. Right now the Adapter constructor is passed in, not a constructed adapter. socket.io constructs the adapter. So, there's no good way for the end user...

@darrachequesne I don't think that there's anything inherently wrong with socket.io controlling the adapter lifecycle. I just think that in that case, the adapter needs an opportunity to start long...

Hey, I just got back to trying to implement these changes on my end. Is `init` ever being called? I can't find a call to it, and my debug messages...

``` return gulp.src(source) .pipe(sourcemaps.init()) .pipe(ts({ noExternalResolve: true, target: "ES6" })) .pipe(babel({ presets: ["es2015"] })) .pipe(concat("ff-app.js")) .pipe(sourcemaps.write({ includeContent: false, sourceRoot: "/" })) .pipe(gulp.dest(paths.scriptDist)); ```