but if i am currently pulling from org.apache, does it mean everything is going to be the same if i just pull from npm? Because i dont want to break anything
You will have to do some testing, and with several plugins, you will even have to make code changes, since the interface changed.
The plugins at the pgb repo haven't been updated/mantained for about a year, now. Newer versions have only been published at npm.
Wondering the org.apache.cordova plugins like contacts/device (the core plugins)....etc if no source is assigned are they are pgb or npm???
Depends. If you used the old gap: namespaced plugin element, I believe they were taken from the old pgb repo. If you u sed the plugin element without namespace and provided no source repo, they were name-converted and then taken from npm, already.
Thanks for the reply, i just tested all the plugin except the CORE org.apache.cordova are all using npm. The only ones i have left are these
<gap:plugin name="org.apache.cordova.device" />
Are these the one you refered to be name-converted?
Cool thanks, i just took a look at the doc, referencing like this, is all good?
<plugin name="org.apache.cordova.vibration" source="npm"/>
even if i am not using the name cordova-plugin-vibration?
I think it's a bad idea to specifiy something different from what you want. You should use the npm-style name of the plugin!
That said, you can see for yourself if this renders the desired result. Build it with the line you quoted above, then see in your PGB app's plugins list (or in the build log) what is actually retrieved and included.
It willl most likely be the latest version of the plugin from npm, but this behaviour is not clearly documented anywhere, so I doubt if it should be relied on.
a blog post will be out friday outlining the changes that will occur on nov 15th.
- if you used a versioned core plugin from our repo then it will be identical to the same version on npm.
- i would not use org.apache.cordova.* as it is using a translation to get the new name and i can see that being removed.
To add to this if you go to the Plugins tab of your App on the Build site, it should list the versions you are using, which should help you migrate to npm.