2013/5/26 George Stagas <[email protected]>: > 2013/5/26 Marco Rogers <[email protected]>: >> It's not clear from this thread what you want exactly. You want to name your >> modules whatever you want, not use namespaces, have them on npm, and also >> avoid name collision? How exactly do you see that working? >> >> :Marco >> > > I'm sorry, we lost it somewhere in the middle. I just want my code to > read properly like var merge = require('merge'); not 'stagas-merge' > and this issue is solved by npm as Göktuğ pointed out but now my other > issue that came up is that by not publishing to npm and using github > paths it kills discoverability. So I think, so that everyone is happy, > we need to find a way to index these along with the regular node > modules search, which is unfortunately tied to npm atm. >
A hackish solution that pops in my mind is to have a dummy module 'stagas-merge' that requires the gh stagas/merge and reexports it, so that I can publish it and be indexed, but that's not ideal. > >> On Saturday, May 25, 2013 11:06:28 AM UTC-7, stagas wrote: >>> >>> 2013/5/25 Alex Kocharin <[email protected]>: >>> > >>> >> Whoever likes can publish to npm, whoever likes can push to Github. >>> >> Both >>> >> should be given equal chance of discovery though. >>> > >>> > Github is a tool for development, npm registry is a tool for deployment. >>> > Am >>> > I missing something here? By the way, mix of those two is very well >>> > known to >>> > create serious trouble (https://github.com/isaacs/npm/issues/1727). >>> > >>> > Also, there was a holywar in npm issues about namespacing... I guess >>> > anything about "proper naming" has been said there already: >>> > https://github.com/isaacs/npm/issues/798 >>> > >>> >>> They're both public data containers that you upload stuff into. One >>> has a single namespace, the other has a username-based namespace. >>> What's for "deployment" and what's for "development" are purely >>> personal choices. >>> >>> > >>> > On Saturday, May 25, 2013 3:49:36 PM UTC, stagas wrote: >>> >> >>> >> 2013/5/25 Alex Kocharin <[email protected]>: >>> >> > >>> >> > It's an answer to unrelated question. If a package is intended to be >>> >> > used in >>> >> > public, it should be in public registry (npmjs.org). If it's for >>> >> > internal >>> >> > use, github will do fine. >>> >> > >>> >> > But namespaces could do the job if you publish a package with a name >>> >> > like >>> >> > "stagas.merge". It's quite uncommon though. >>> >> > >>> >> >>> >> I want both visibility and proper naming. That logic isn't valid. >>> >> Github is very public. We just need to find a way to index these along >>> >> with the rest npm modules. Whoever likes can publish to npm, whoever >>> >> likes can push to Github. Both should be given equal chance of >>> >> discovery though. >>> >> >>> >> > >>> >> > >>> >> > On Saturday, May 25, 2013 1:39:19 PM UTC+4, Jonathan Ong wrote: >>> >> >> >>> >> >> just don't bother publishing it. use github namespaces in npm. >>> >> >> >>> >> >> { >>> >> >> "dependencies": { >>> >> >> "merge": "stagas/merge" >>> >> >> } >>> >> >> } >>> >> >> >>> >> >> On Saturday, May 25, 2013 1:34:51 AM UTC-7, Alex Kocharin wrote: >>> >> >>> >>> >> >>> >>> >> >>> RPG name generator could do the job. :) >>> >> >>> >>> >> >>> -- >>> >> >>> // alex >>> >> >>> >>> >> >>> 25.05.2013, 10:49, "George Stagas" <[email protected]>: >>> >> >>> > Hi all, >>> >> >>> > >>> >> >>> > I really want to name my modules however I like and be >>> >> >>> > installable >>> >> >>> > and >>> >> >>> > require-able. >>> >> >>> > >>> >> >>> > For example, I want to write a 'merge' utility, and I don't want >>> >> >>> > to >>> >> >>> > struggle coming up with a random set of letters because I want my >>> >> >>> > code >>> >> >>> > to read require('merge') not require('golalamergifiable'). >>> >> >>> > >>> >> >>> > What are my options currently? Anyone have any solutions? >>> >> >>> > >>> >> >>> > -- >>> >> >>> > -- >>> >> >>> > 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 >>> >> >>> > >>> >> >>> > --- >>> >> >>> > You received this message because you are subscribed to the >>> >> >>> > Google >>> >> >>> > Groups "nodejs" group. >>> >> >>> > To unsubscribe from this group and stop receiving emails from it, >>> >> >>> > send >>> >> >>> > an email to [email protected]. >>> >> >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >> > >>> >> > -- >>> >> > -- >>> >> > 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 >>> >> > >>> >> > --- >>> >> > You received this message because you are subscribed to the Google >>> >> > Groups >>> >> > "nodejs" group. >>> >> > To unsubscribe from this group and stop receiving emails from it, >>> >> > send >>> >> > an >>> >> > email to [email protected]. >>> >> > For more options, visit https://groups.google.com/groups/opt_out. >>> >> > >>> >> > >>> > >>> > -- >>> > -- >>> > 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 >>> > >>> > --- >>> > You received this message because you are subscribed to the Google >>> > Groups >>> > "nodejs" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> > an >>> > email to [email protected]. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> > >>> > >> >> -- >> -- >> 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 >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
