In the last few days I played around with a local npm registry mirror, and I went through some code from the NPM tool and related utility modules.
I found out that the current HTTP API exposed from the npm registry is too tied to the CouchDB HTTP API, especially regarding authentication, authorization and module updates (e.g. attachments API). Some parts of the API, on the other hand, are not really useful to the core usage of the npm tool, and I think they are mainly there to satisfy the needs of the npmjs.org website (e.g. stars by users, stars by package, latest packages, etc.). I think that the whole ecosystem could benefit from a standardization of the core HTTP API. If we define the behaviour that the npm tool expects to correctly work, and the core functionalities that must be supported, it could be way easier to implement different variations of an npm server. Given a stable API, different implementations of the npm server could be written, with different options about data storage, additional features, different authentication methods and so on. I hope that in the (near) future a community effort could be done to produce a stable version of the npm API. What do you think about it? -- -- 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.
