When are releases usually done? Can we get a release to fix the NTLM + TLS bug?

[rocketmonkeys]

I just did some digging, and finally found this issue/PR which fixes my problem:

https://github.com/tediousjs/tedious/issues/338

https://github.com/tediousjs/tedious/pull/367/commits/60aefbbe1a92dba795665ed2d55a12387766e219

Those are merged into master, but aren't in the last (v1.14.0) release.  I'd love to get a release so I can use windows-auth w/ my sql boxes.  What's the process like for that?  Is there any way to help that process along?

Thanks!

[Simon Hooker]

Hi there,

Following trying to get validation of certificates in I am hitting this same issue.  I have raised an issue for it ( https://github.com/tediousjs/tedious/issues/422 ) as well as doing a bit of a hacky "fix" on my fork.  If you use the following line to install from that branch you will get the current master head including all merged changes since 1.14.0.

npm install git+https://github.com/SimonHooker/tedious.git#issue-422

I don't propose that this is an ideal solution but it feels like it solves the issue enough for me to get use of the changes I need whilst releases or a more permanent change that can provide a postinstall hook are put together.

The key issue is multiple.  Firstly, the .npmignore prevents the /scripts and /src directories from being pulled down.  Secondly, the prepublish hook is not executed and so the /src directory is not generated into the /lib directory.