npm publish about node-sonos-discovery

[GermanBluefox]

I must say even more, if he will not do that. I will make it and give him
the rights.
Because last change with static port 8083 broke my connection and to avoid
it at least npm release would be nice.
Very cool project, but static port should be removed.

Greetings,
Bluefox
7 Июл 2016 г. 15:42 пользователь "Daniel Becker" [email protected]
написал:

Hi,

Why are you not publishing on npm?

Greetings

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#87, or mute the
thread
https://github.com/notifications/unsubscribe/AEXqgL5Z9r483S06qBo54NBpjD9es0T0ks5qTQJJgaJpZM4JHFwf
.

[GermanBluefox]

Ok I mean port 8080.
7 Июл 2016 г. 18:27 пользователь "Bluefox Fox" [email protected]
написал:

I must say even more, if he will not do that. I will make it and give him
the rights.
Because last change with static port 8083 broke my connection and to avoid
it at least npm release would be nice.
Very cool project, but static port should be removed.

Greetings,
Bluefox
7 Июл 2016 г. 15:42 пользователь "Daniel Becker" [email protected]
написал:

Hi,

Why are you not publishing on npm?

Greetings

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#87, or mute the
thread
https://github.com/notifications/unsubscribe/AEXqgL5Z9r483S06qBo54NBpjD9es0T0ks5qTQJJgaJpZM4JHFwf
.

[ColdFireIce]

What static port? The current version tries to find an unused port on the system for the event-callbacks, and on Sonos-systems, it's always :1400

[jishi]

The static port relates to the web-controller, not discovery.

The reason for not publishing on npm has been that I can not guarantee support nor updates to it, and I personally find it highly annoying when people publish crap on public repositories that gets abandoned within months :) I didn't want to be equally bad.

I however have considered publishing the new version, but only the discovery library (I don't think npm is the place for actual applications), if I can iron out all quirks and also be more strict in my versioning and keeping backward compatibility.