On Tue, Sep 23, 2014 at 4:17 AM, Joachim Gleissner wrote:

Hi Marguerite,

On Mon, 22 Sep 2014 22:58:40 +0800 "marguerite" wrote:

...

...

Yes, of course. I actually wanted to do that on Friday but had to leave the office on short notice.

I'm working on it. and sent some of the packages Factory... there're still 50% packages unsent.

Ok, cool.

...

...

I agree in theory that having a generic installation method is preferable to doing it manually, however the npm local install command has its downside too IMHO. npm install simply copies the whole package into the node_modules directory, including documentation, test files, potentially included packages the package depends on, even dotfiles like .gitignore. This means you have to manually clean up after npm anyway, which kinda defeats the point of using it.

Unlikely I found that...so forgot what I've said.

Once concern is:

Dependencies to bootstrap NPM are about 100 nodejs packages.

And it's growing. e.g. nodejs-request has new version, which introduces 10 dependencies, which further introduces another 10 dependencies...

So do an update for npm is really painful now...

Another concern is:

Maybe the update doesn't mean to update everything to the latest verisons. e.g. If npm wants some specific versions...that'll be painful again...

By now we didn't take the version requirements in package.json into consideration, So if someday bugs happened because of that, it might be impossible to debug so many Javascripts...

Both true. I find packaging node.js modules generally quite tedious. They are often very small, sometimes just one js file with one function in it, but it's the way it is. I don't really have a good idea to do it differently.

However, to deal with the large number of packages I had to submit, I wrote a script to fetch module information from registry.npmjs.org, download the tarball, and generate the spec file. It's a bit basic at the moment (e.g. it doesn't take version numbers of dependencies into account), but I guess it could be extended to handle that and also to handle updates rather than new packages only. Due npm registry and the (mostly) uniformity of node modules, those tasks are fairly well scriptable which could take some of the pain away. I'll look into it.

Is this script you mention available? I've been holding off on packaging a few nodejs packages, puppet-explorer specifically, due to not wanting to get into the dependency nodejs hell that npm was about to unleash. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Thu, Sep 25, 2014 at 9:57 AM, Joachim Gleissner wrote:

Hi,

On Tue, 23 Sep 2014 12:15:22 -0400 Darin Perusich wrote:

[...]

...

...

However, to deal with the large number of packages I had to submit, I wrote a script to fetch module information from registry.npmjs.org, download the tarball, and generate the spec file. It's a bit basic at the moment (e.g. it doesn't take version numbers of dependencies into account), but I guess it could be extended to handle that and also to handle updates rather than new packages only. Due npm registry and the (mostly) uniformity of node modules, those tasks are fairly well scriptable which could take some of the pain away. I'll look into it.

Is this script you mention available? I've been holding off on packaging a few nodejs packages, puppet-explorer specifically, due to not wanting to get into the dependency nodejs hell that npm was about to unleash.

I haven't looked into writing a more general-purpose node.js packaging script yet. So far I only have that script to create new node packages. If that's of any use for you, I can send it to you.

That would be useful, please send it ;-) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org