Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 08/01/13 20:49, T.C. Hollingsworth wrote: Not much different than e.g. Python's easy_install/pip and RPM. You can install packages using both RPM/yum and npm, and `npm install -g` can possibly get you into trouble just like `easy_install` outside a virtualenv can. With pip (run as normal user) I can install in $HOME/.local/lib/python*/site-packages/ so that the system-wide installed packages are not touched, but all projects created by user can use them. Can I do something like that with npm? Matěj -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 01/09/2013 08:55 AM, Matej Cepl wrote: On 08/01/13 20:49, T.C. Hollingsworth wrote: Not much different than e.g. Python's easy_install/pip and RPM. You can install packages using both RPM/yum and npm, and `npm install -g` can possibly get you into trouble just like `easy_install` outside a virtualenv can. With pip (run as normal user) I can install in $HOME/.local/lib/python*/site-packages/ so that the system-wide installed packages are not touched, but all projects created by user can use them. Can I do something like that with npm? Matěj It looks like you can choose where do you wish install (locally, globally). I would leave the decision about Fedora setting to those who use node.js. Marcela -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 1/9/13, Matej Cepl mc...@redhat.com wrote:
On 08/01/13 20:49, T.C. Hollingsworth wrote:
Not much different than e.g. Python's easy_install/pip and RPM. You
can install packages using both RPM/yum and npm, and `npm install -g`
can possibly get you into trouble just like `easy_install` outside a
virtualenv can.
With pip (run as normal user) I can install in
$HOME/.local/lib/python*/site-packages/ so that the system-wide
installed packages are not touched, but all projects created by user can
use them. Can I do something like that with npm?
Yes and no. I think there's a bit of confusion on how the node module
loader actually works, so I'll provide a concrete example.
Say your working on the Next Big WebApp, in ~/nbw/, and you want to
use the express web framework, which we don't have packaged in Fedora
yet, and the async library, which we do. You would just `cd ~/nbw/`,
`npm install express` to install express from the npm registry (and
also install express' dependencies into
~/abw/node_modules/express/node_modules, and so on recursively) into
~/nbw/node_modules/express, and then `npm link async` to effectively
`ln -sf /usr/lib/node_modules/async ./node_modules/async`. You can
then create an e.g. 'app.js' file and require('express') and 'async'
to your hearts content. However, you can't require('inherits'), even
though /usr/lib/node_modules/inherits exists, because node has no
notion of a global module loading path. Everything must be explicitly
provided in ~/abw/node_modules, whether its an actual module tree or a
symlink to one somewhere else on the system.
So you probably wouldn't want to create a '~/.local/lib/node_modules'
directory., though you could `export
NODE_PATH=/usr/lib/node_modules:~/.local/lib/node_modules' if that's
*really* what you want.
The motivation behind this is explained somewhat in the npm FAQ:
https://npmjs.org/doc/faq.html#I-installed-something-globally-but-I-can-t-require-it
-T.C.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
why am not in https://fedoraproject.org/wiki/Features/NodeJS If i was the first one on start with NODEJS package On Tue, Jan 8, 2013 at 12:12 PM, Jaroslav Reznik jrez...@redhat.com wrote: As decided by FESCo on 2012-12-05 meeting, all proposed Features are required to pass through the community review by announcing them on devel-announce list. FESCo votes on new features no sooner than a week from the announcement. = Features/NodeJS = https://fedoraproject.org/wiki/Features/NodeJS * Detailed description: Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. Jaroslav ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
why am not in https://fedoraproject.org/wiki/Features/NodeJS If i was the first one on start with NODEJS package On Tue, Jan 8, 2013 at 12:40 PM, Adrian Alves aal...@gmail.com wrote: why am not in https://fedoraproject.org/wiki/Features/NodeJS If i was the first one on start with NODEJS package On Tue, Jan 8, 2013 at 12:12 PM, Jaroslav Reznik jrez...@redhat.comwrote: As decided by FESCo on 2012-12-05 meeting, all proposed Features are required to pass through the community review by announcing them on devel-announce list. FESCo votes on new features no sooner than a week from the announcement. = Features/NodeJS = https://fedoraproject.org/wiki/Features/NodeJS * Detailed description: Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. Jaroslav ___ devel-announce mailing list devel-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 01/08/2013 10:40 AM, Adrian Alves wrote: why am not in https://fedoraproject.org/wiki/Features/NodeJS If i was the first one on start with NODEJS package The list of people on that page is volunteer-added. If you would like to help on this, please feel free to add your name to the list. If you do so, you're committing to helping to make sure the package makes is into Fedora 19. I couldn't find you to ask when I was setting up that page. We're happy to have your help. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 01/08/2013 03:59 PM, Stephen Gallagher wrote: On 01/08/2013 10:40 AM, Adrian Alves wrote: why am not in https://fedoraproject.org/wiki/Features/NodeJS If i was the first one on start with NODEJS package The list of people on that page is volunteer-added. If you would like to help on this, please feel free to add your name to the list. If you do so, you're committing to helping to make sure the package makes is into Fedora 19. I couldn't find you to ask when I was setting up that page. We're happy to have your help. I thought Lubomir Rintel a.k.a lkundrak had been working on this [1]? Was he not contacted either? JBG 1. http://fedoraproject.org/wiki/User:Lkundrak/NodeJS -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On Tue, Jan 8, 2013 at 4:12 PM, Jaroslav Reznik jrez...@redhat.com wrote: = Features/NodeJS = https://fedoraproject.org/wiki/Features/NodeJS From Summary: The Node.js JavaScript runtime and associated ecosystem, including the npm package manager. Could you describe more detail the interaction of npm and rpm packaging, please? At least the how to test section suggests that npm will be the preferred packaging mechanism, which is different from how other language-specific packaging systems are treated. Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On 1/8/13, Jóhann B. Guðmundsson johan...@gmail.com wrote: I thought Lubomir Rintel a.k.a lkundrak had been working on this [1]? Was he not contacted either? The last time he was contacted (during my original packaging effort) regarding it he said he was disgusted with it and since FESCo recently reassigned ownership of all his packages I figured there was no need to bother him about it again. JBG 1. http://fedoraproject.org/wiki/User:Lkundrak/NodeJS -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Proposed F19 Feature: NodeJS - The JavaScript runtime and associated ecosystem, including the npm package manager
On Tuesday, January 8, 2013, Miloslav Trmač m...@volny.cz wrote: On Tue, Jan 8, 2013 at 4:12 PM, Jaroslav Reznik jrez...@redhat.com wrote: = Features/NodeJS = https://fedoraproject.org/wiki/Features/NodeJS From Summary: The Node.js JavaScript runtime and associated ecosystem, including the npm package manager. Could you describe more detail the interaction of npm and rpm packaging, please? Not much different than e.g. Python's easy_install/pip and RPM. You can install packages using both RPM/yum and npm, and `npm install -g` can possibly get you into trouble just like `easy_install` outside a virtualenv can. The upside is that Node/npm use a sort of virtualenv-by-default setup whereupon all modules must explicitly provide their dependencies in a node_modules directory. System RPMs accomplish this by just symlinking to the other modules, but developers working on their own projects have the option of `npm install`ing the npm version of the module or `npm link`ing the system version into their project. At least the how to test section suggests that npm will be the preferred packaging mechanism, which is different from how other language-specific packaging systems are treated. It's only preferred right now in the sense that we can't possibly package all 20,000+ modules in the npm registry in 6 months, so users interested in Node will most likely have to get what they want via npm for the time being. Even if we did, developers will still want to use some featurtes of npm for the reasons mentioned above. Mirek -T.C. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
