`npm help link`
On Thu, Sep 19, 2013 at 9:03 PM, David Kemp <drk...@google.com> wrote: > +1 for project specific registry (not home dir) > > > On Thu, Sep 19, 2013 at 2:59 PM, Braden Shepherdson <bra...@chromium.org > >wrote: > > > One alternative is to symlink it into $HOME/.plugman/cache/my.plugin.id. > > Then plugman when fetching it will use that, assuming the version is new > > enough. I think the right place for the file is in > > ~/.plugman/localRegistry.json or similar, since fetching plugins is > > definitely plugman's responsibility and not CLI's. > > > > Braden > > > > > > On Thu, Sep 19, 2013 at 2:56 PM, Andrew Grieve <agri...@chromium.org> > > wrote: > > > > > The logic is: > > > - If there's a url, use it, otherwise use the registry. > > > > > > If I'm developing on a plugin, and that plugin has a dependency, I > don't > > > want it fetching it from the registry. I could change the <dependency> > to > > > have a url= to the local path, but then I need to remember to take that > > out > > > before publishing. > > > > > > So... I'm thinking it would be useful to allow projects to provide > their > > > own file-backed local registry. E.g. a JSON file of pluginId -> > url/path. > > > Where the new algorithm would be: > > > > > > if id in localRegistry, use that url, otherwise, use the registry. > > > > > > I think this will be super useful for projects that want to distribute > > > plugins off-registry as well. > > > > > > Question is - where's the best place for this? > > > > > > My first thought was in CLI's .cordova/config.json, but that won't work > > for > > > plugman projects. homedir may address some use-cases, but > > project-specific > > > local registry is still important I think. So... Maybe for CLI > projects, > > we > > > put it in .cordova/config.json and for plugman you use a > > > --localregistry=FILE flag? > > > > > >
