update tunnel dependency for late node js support

[wzrdtales]

see title, simple dependency upgrade

If not merged or no communication the date when hardfork occurs is going to be 01 July 2016

[wzrdtales]

The hard fork date btw. is not ment to be rude just an information b/c this repo seems to be pretty dead.

[michael-tamse]

Any news? I would like to add

  var opts = {
    proxy: _.pick(conf, 'host','port','protocol','localAddress','proxyAuth'),
    maxSockets: conf.sockets
  };

(emphasis on ,'proxyAuth')
to line 141 in index.js ... with this change I'm able to authenticate proxy via proxyAuth: 'userId:password' in initialize.

[wzrdtales]

@MiShibari This clearly slipped off my mind ;)

Hard fork goes here:
https://github.com/np-maintain/global-tunnel

May be I go invest some time to fix it for later versions > 0.10. Currently it is broken on those.

[wzrdtales]

Or at least the tests fail for > 0.10. It seems like it does work on those versions though.

[alvarollmenezes]

Please update the dependency. Not working on latest node versions.

[wzrdtales]

@alvarollmenezes This repo is near to dead, it is unlikely to get any further responses. Also salesforce has recently moved it, a month ago, but it does not seem that they plan to maintain it.

[alvarollmenezes]

@wzrdtales That's unfortunately. It solved a major problem when using dependencies that rely purely on http(s).request in my organization. Forked the repo anyway

[wzrdtales]

@alvarollmenezes That is why I announced to hard fork it, also it slipped my mind. But actually it is here https://github.com/np-maintain/global-tunnel

I probably wont develop on it unless I have need for this, but at least I will review PRs and give the community the chance to evolve this module. Although that someone would probably first need to rewrite the tests, as those are broken on everything later than 0.10

It is not uncommon that packages become unmaintained at some time. Shift of interest and time are often a reason for this and that is completely okay though.

How ever, if you want you can use my hard fork. If we're in luck, then salesforce is taking care over this module again. At least they seem to have something ongoing internally #18 and may be someone takes time for long abandoned packages or at least they actively search for new maintainers, which would be probably the best for the module.