[Pkg-javascript-devel] Bug#622628: Bug#622628: Bug#622628: Bug#622628: npm no longer works

[Jérémy Lal]

On 08/03/2012 15:33, Jonas Smedegaard wrote:
> On 12-03-08 at 10:34am, Felipe Sateler wrote:
>> On Tue, Mar 6, 2012 at 13:42, Jonas Smedegaard <dr at jones.dk> wrote:
>>> On 12-03-06 at 01:14pm, Felipe Sateler wrote:
>>>> npm is too old to function with current nodejs in debian. Please 
>>>> update the package!
>>>>
>>>> I might (hopefully...) have time to help, and I will need this. Is 
>>>> there any roadmap on what is missing to get an updated npm package?
>>>
>>> Great!
>>>
>>> Pull the git and see the notes in changelog about what's missing.
>>
>> One of the important parts is to replace the node_modules by a package 
>> of their own.
>> I propose to do otherwise, and just include them. When the modules get 
>> packaged on their own, strip them from npm.

A few notes :
* node-uuid and request have debian packages already
  npm 1.1.4 depends on node-request >= 2.9.153 (waiting to be uploaded)
* npm author is the author of all other modules except "mkdirp"
* some modules are very useful and popular, they must be packaged,
  others like "slide" or "inherits" are small and probably used by npm only
  (i am still trying to figure out how to find reverse dependencies in npm).


>> BTW, npm upstream is now distributed as part of node.js. Does it make 
>> sense to split it? IMO, it makes more sense to distribute it as 
>> upstream, this should eliminate the incompatibilities we see in the 
>> current npm package with current nodejs.

npm is a development tool, for developers; it is absolutely not
necessary to have it to use nodejs.

> Is it now maintained by same upstream author, using same release 
> schedule as Node itself?

Same release manager (Isaac), but different versions.

> Or does it still have a separate project home 
> and is just includes as a convencience copy with Node?

Convenience copy.

> If the latter, I strongly recommend to maintain it as a separate 
> project.

+10

Jérémy.