ircanywhere / irc-factory

A rebuilt irc-factory from simple-irc-socket and irc-message. Get support at #ircanywhere on freenode
https://ircanywhere.com
MIT License
60 stars 14 forks source link

Can't npm install #1

Closed silverbucket closed 10 years ago

silverbucket commented 10 years ago

Hi, I'm looking for a replacement to the buggy node-irc module and came across your library.

I'm wondering whether is this stable and ready for use?

I tried to install it...

$ npm install irc-factory
npm WARN package.json JSV@4.0.2 'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json crypto@0.0.3 crypto is also the name of a node core module.
npm WARN package.json mail@0.2.3 No repository field.
npm http GET https://registry.npmjs.org/irc-factory
npm http 304 https://registry.npmjs.org/irc-factory
npm http GET https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz
npm http 404 https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz
npm ERR! fetch failed https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR!     at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at fs.js:1596:14
npm ERR!     at /usr/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR!     at Object.oncomplete (fs.js:107:15)
rickihastings commented 10 years ago

It's quite lightweight so it's hopefully fairly stable and has a lot of tests, although it's new and constantly getting updated. It should work via npm install if not try putting the latest version in your package.json and running an npm install.

On 17 Dec 2013, at 14:59, Nick Jennings notifications@github.com wrote:

Hi, I'm looking for a replacement to the buggy node-irc module and came across your library.

I'm wondering whether is this stable and ready for use?

I tried to install it...

$ npm install irc-factory npm WARN package.json JSV@4.0.2 'repositories' (plural) Not supported. npm WARN package.json Please pick one as the 'repository' field npm WARN package.json crypto@0.0.3 crypto is also the name of a node core module. npm WARN package.json mail@0.2.3 No repository field. npm http GET https://registry.npmjs.org/irc-factory npm http 304 https://registry.npmjs.org/irc-factory npm http GET https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz npm http 404 https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz npm ERR! fetch failed https://registry.npmjs.org/irc-factory/-/irc-factory-1.1.4.tgz npm ERR! Error: 404 Not Found npm ERR! at WriteStream. (/usr/lib/node_modules/npm/lib/utils/fetch.js:57:12) npm ERR! at WriteStream.EventEmitter.emit (events.js:117:20) npm ERR! at fs.js:1596:14 npm ERR! at /usr/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:103:5 npm ERR! at Object.oncomplete (fs.js:107:15) — Reply to this email directly or view it on GitHub.

silverbucket commented 10 years ago

I tried that as well, still giving the same error. The output shows it trying to fetch version 1.1.4 and that's the latest version correct?

rickihastings commented 10 years ago

Yes correct. Looks like either an npm issue or something. I'll be at my computer in about 15 minutes and I'll have a better look at what's going on for you.

On 17 Dec 2013, at 15:11, Nick Jennings notifications@github.com wrote:

I tried that as well, still giving the same error. The output shows it trying to fetch version 1.1.4 and that's the latest version correct?

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

rickihastings commented 10 years ago

Ok, it seems to be working fine for me:

vagrant@precise32:~/shared/project$ npm install irc-factory
npm http GET http://registry.npmjs.org/irc-factory
npm http 200 http://registry.npmjs.org/irc-factory
npm http GET http://registry.npmjs.org/eventemitter2/0.4.13
npm http GET http://registry.npmjs.org/irc-message/0.2.0
npm http GET http://registry.npmjs.org/irc-socket/1.3.1
npm http GET http://registry.npmjs.org/axon/1.0.0
npm http GET http://registry.npmjs.org/underscore/1.5.2
npm http 200 http://registry.npmjs.org/irc-message/0.2.0
npm http GET http://registry.npmjs.org/irc-message/-/irc-message-0.2.0.tgz
npm http 200 http://registry.npmjs.org/irc-socket/1.3.1
npm http GET http://registry.npmjs.org/irc-socket/-/irc-socket-1.3.1.tgz
npm http 200 http://registry.npmjs.org/underscore/1.5.2
npm http 200 http://registry.npmjs.org/eventemitter2/0.4.13
npm http GET http://registry.npmjs.org/underscore/-/underscore-1.5.2.tgz
npm http GET http://registry.npmjs.org/eventemitter2/-/eventemitter2-0.4.13.tgz
npm http 200 http://registry.npmjs.org/axon/1.0.0
npm http GET http://registry.npmjs.org/axon/-/axon-1.0.0.tgz
npm http 200 http://registry.npmjs.org/irc-message/-/irc-message-0.2.0.tgz
npm http 200 http://registry.npmjs.org/irc-socket/-/irc-socket-1.3.1.tgz
npm http 200 http://registry.npmjs.org/eventemitter2/-/eventemitter2-0.4.13.tgz
npm http 200 http://registry.npmjs.org/underscore/-/underscore-1.5.2.tgz
npm http 200 http://registry.npmjs.org/axon/-/axon-1.0.0.tgz
npm http GET http://registry.npmjs.org/debug
npm http GET http://registry.npmjs.org/configurable/0.0.1
npm http GET http://registry.npmjs.org/escape-regexp/0.0.1
npm http 200 http://registry.npmjs.org/configurable/0.0.1
npm http GET http://registry.npmjs.org/configurable/-/configurable-0.0.1.tgz
npm http 200 http://registry.npmjs.org/escape-regexp/0.0.1
npm http GET http://registry.npmjs.org/escape-regexp/-/escape-regexp-0.0.1.tgz
npm http 200 http://registry.npmjs.org/debug
npm http 200 http://registry.npmjs.org/escape-regexp/-/escape-regexp-0.0.1.tgz
npm http 200 http://registry.npmjs.org/configurable/-/configurable-0.0.1.tgz
irc-factory@1.1.4 node_modules/irc-factory
âââ irc-socket@1.3.1
âââ eventemitter2@0.4.13
âââ underscore@1.5.2
âââ irc-message@0.2.0
âââ axon@1.0.0 (escape-regexp@0.0.1, debug@0.7.4, configurable@0.0.1)
vagrant@precise32:~/shared/project$

Maybe try a npm cache clear

silverbucket commented 10 years ago

OK, it finally worked after trying directly with wget (which still failed due to a certificate mismatch) then trying npm again. Not sure what the issue was but it was likely something with registry.npmjs.org and not with the irc-factory package.

rickihastings commented 10 years ago

Yeah ok thats good, a git clone into node_modules would have done the job too, although slightly hacky. Npm has been having problems lately so I'm putting it down to that. I thought it was an issue with the fact I'd published the module to http://registry.npmjs.org and not https://registry.npmjs.org but I've just changed my settings and it's worked again for me.

Feel free to give me a shout if you need any help with the package, it's still a WIP. You can check out the source at https://github.com/ircanywhere/ircanywhere/tree/development/server for some more detailed examples of how to use it to it's full potential.

silverbucket commented 10 years ago

Hmm, so irc-factory is not a stand-alone irc client, but needs the ircanywhere server as well?

rickihastings commented 10 years ago

Oh, no not at all. I've made a more detailed explanation of it in #2. The ircanywhere server is just an example of how to use it. If you're planning on using the persistance, you'll need to also include axon in your package. Although I'm thinking of making this available via require('irc-factory').axon or something.