Scopes are like namespaces. In the reverse domain name world, org.apache.cordova was considered a namespace, right ?
We did not want non core packages to publish to that namespace, so does the same argument apply ? Alternatively, we can think of scope as packages that apply to a particular environment - for example, all cordova packages would be @cordova scope. -----Original Message----- From: Michal Mocny [mailto:mmo...@google.com] Sent: Monday, April 20, 2015 2:03 PM To: dev Subject: Re: Scoped package names for npm? Other questions to answer: - Can 3rd-parties publish to this scope? - Do we want them to? - Do we want to default to @cordova scope if none is provided, such that you could do `cordova plugin add device`? -Michal On Mon, Apr 20, 2015 at 5:00 PM, Michal Mocny <mmo...@google.com> wrote: > https://docs.npmjs.com/getting-started/scoped-packages > > Should we be @cordova/plugin-device instead of cordova-plugin-device? > > -Michal >
