cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: Update: Plugins to NPM (Phase 1)
Date Wed, 11 Mar 2015 14:30:47 GMT
On Wed, Mar 11, 2015 at 10:10 AM, Andrew Grieve <agrieve@chromium.org>
wrote:

> On Mon, Mar 9, 2015 at 8:20 PM, Steven Gill <stevengill97@gmail.com>
> wrote:
>
> > Our master branch has plugin fetching from npm set as the fallback now.
> It
> > will go directly to npm if the plugin-id entered isn't reverse domain
> name
> > style. Cordova-lib also warns users to use the package-name instead of
> > plugin-id when adding plugins that we have renamed and are in
> > https://github.com/stevengill/cordova-registry-mapper
> >
> > Plugins TODO:
> >
> > - README: Move doc/en/index.md into README.md. Delete doc/en/index.md.
> Add
> > links in README.md that point to github page of translated docs for
> plugin.
> > (ex.
> >
> https://github.com/apache/cordova-plugin-device/blob/master/doc/es/index.md
> > ).
> > I'd love to hear from someone (Victor?) working on docs translations
> about
> > how this change will impact them.
> >
> > - Rename plugin-ids to new plugin names in plugin.xml. Anything we should
> > be aware of before we do this? (Ex. rename org.apache.cordova.device to
> > cordova-plugin-device in plugin.xml)
> >
> Will need to update JS / native references where plugins depend on each
> other (e.g. in require()s). Think there are only a couple.
>

Should make sure the mapper does this automatically for js require(), but
we should still update core plugins to not rely on it.

For native side plugin deps, we will need to make the updates.


>
>
> >
> > - Add peer dependencies to plugins that depend on other plugins (file,
> > media-capture, etc)
> >
> > - Paramedic support for every plugin
> >
> > - Major version bump for all core plugins
> >
> > - Update plugins release process to use package.json version as main
> > version and have it update plugin.xml's version. Will do this when we do
> > next release
> >
> > Migration TODO:
> >
> > - Create blog post talking about migration to npm for community
> >
> > - include how we are renaming, suggest they do so if they want to. Will
> > suggest they follow the pattern cordova-plugin-*
> >
> > - mention https://github.com/stevengill/cordova-registry-mapper for
> > warning
> > purposes
> > - include potential lifespan of CPR (publishing and read only)
> > - Discuss plugman createpackage.json command
> > - Discuss keyword: 'ecosystem:cordova'
> >
> >
> > Thoughts? Missing anything?
> >
>

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