search

peers / peerjs

Simple peer-to-peer with WebRTC.
https://peerjs.com
MIT License
12.48k stars 1.43k forks source link

Publish current version to NPM #85

Closed Fauntleroy closed 11 years ago

Fauntleroy commented 11 years ago

npmjs.org is telling me: "0.2.0 last updated 7 months ago".

package.json is telling me 0.3.0.

Does this mean the version on npm is out of date? If so, can we get it updated (and keep it that way)?

michelle commented 11 years ago

Hey, so the peerjs on npm is the server component which doesn't have the same versioning as the library. Arguably this shouldn't be the case and both the library and peerserver should both be on npm, so I'll look into getting this fixed.

Thanks!

On Saturday, October 12, 2013, Timothy Kempf notifications@github.com wrote:

npmjs.org is telling me: "0.2.0 last updated 7 months ago".

package.json is telling me 0.3.0.

Does this mean the version on npm is out of date? If so, can we get it updated (and keep it that way)?

— Reply to this email directly or view it on GitHub.

Sent from Gmail Mobile

ericz commented 11 years ago

Note that the client library is not on NPM because WebRTC really work with Node yet (this will certainly change as supporting libraries are created / mature)

piranna commented 11 years ago

Note that the client library is not on NPM because WebRTC really work with

Node yet (this will certainly change as supporting libraries are created / mature)

node-webrtc project is getting a huge momentum in the last week, so we could have a working version at the end of the month... :-)

Also, you should consider about creating a npm package for the client since some people use it instead (or in combination with) bower to manage their browser side packages...

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux

ericz commented 11 years ago

Interesting point. Didn't think of that before.

On Sat, Oct 19, 2013 at 12:33 AM, Jesús Leganés Combarro < notifications@github.com> wrote:

Note that the client library is not on NPM because WebRTC really work with

Node yet (this will certainly change as supporting libraries are created / mature)

node-webrtc project is getting a huge momentum in the last week, so we could have a working version at the end of the month... :-)

Also, you should consider about creating a npm package for the client since some people use it instead (or in combination with) bower to manage their browser side packages...

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." – Linus Tordvals, creador del sistema operativo Linux

— Reply to this email directly or view it on GitHubhttps://github.com/peers/peerjs/issues/85#issuecomment-26645309 .

510-691-3951 http://ericzhang.com

Fauntleroy commented 11 years ago

@ericz I use Browserify to do all my package management. You can use npm packages directly with require statements, just like in node. Notably, I use require('socket.io-client') in many projects.

michelle commented 11 years ago

Client library is now available on npm as peerjs: https://npmjs.org/package/peerjs Server is still available as peer: https://npmjs.org/package/peer