Just for test how it work right now.
2012/12/31 Nuno Job <[email protected]> > Have you considered why the repo is not on npm yet? > > The author choose not to publish it yet, I would advise you to to reach > out and ask why at least before using in production. > > I think the appropriate workflow would be something like: > > * If you are a developer of socket.io you already use and know about `npm > link` > * If you have a problem that was patched in master but cant wait for it to > be published, apply a patch to latest stable version. Tell that to the > socket.io folks so they can release a stable version > * If you want to use the bleeding edge version in production, when the > author deliberately choose not to publish, probably a bad idea. > > This is all hypothetical, but then again :) > > Nuno > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
