cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: [Discuss] Cordova-common release
Date Fri, 25 Sep 2015 01:31:26 GMT
Sorry if I take my inner purist theoretical developer out for a minute :-)

The point of having a "node module" it should be explicit and small,
meaning that should be easy to name in a way that describes what it is or

Take into account that "node module" is not the same as a "npm package"

Having 2 npm packages on the npm registry "cordova-common" and
"cordova-lib" to the simple eye would look like duplicate packages, and
then will need to answer multiple times "What is the difference between lib
and common?"

Why not have more smaller explicit npm packages instead?


each one with a index.js exposing APIs

Then the programing model becomes something like this:
var cdvUtil              = require('cordova-util'),
cdvPluginInfo          = require('cordova-plugin-info'),
cdvError                  = require('cordova-error'),
cdvConfigParser     = require('cordova-config-parser'),
cdvConfigChanges = require('cordova-config-changes');

On Thu, Sep 24, 2015 at 12:29 PM Sergey Grebnov (Akvelon) <> wrote:

> Hi guys - we've decided to combine shared logic as cordova-common module
> and publish it separately (read [1] for more details). Corresponding change
> has landed to master[2] on last week so I'm wondering if we should release
> this module and then update LIB to rely on it (similar to cordova-serve).
> So guys it will be great if we can review it one more time (including the
> name - do we all  agree to use cordova-common??)  and then do release -
> I'll be able to help w/ merging the recent changes added to LIB before
> doing release.
> [1]
> [2]
> Thx!
> Sergey
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message