We should definitely do that -- and I think we should release them
simultaneously with cordova-app-hello-world, since it now references
cordova-plugin-whitelist by that name (I had to install it from local git
repo, but it still wasn't a perfectly smooth experience).
On Mon, Mar 23, 2015 at 7:18
from npm?
Leo
-Original Message-
From: iclell...@google.com [mailto:iclell...@google.com] On Behalf Of
Ian
Clelland
Sent: Tuesday, March 24, 2015 6:42 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Whitelist Legacy Whitelist Plugins Release
@1.0.0
, 2015 6:42 AM
To: dev@cordova.apache.org
Subject: Re: [DISCUSS] Whitelist Legacy Whitelist Plugins Release
@1.0.0
We should definitely do that -- and I think we should release them
simultaneously with cordova-app-hello-world, since it now references
cordova-plugin-whitelist by that name
@cordova.apache.org
Subject: Re: [DISCUSS] Whitelist Legacy Whitelist Plugins Release @1.0.0
We should definitely do that -- and I think we should release them
simultaneously with cordova-app-hello-world, since it now references
cordova-plugin-whitelist by that name (I had to install it from local git
repo
+1! Excited to have some npm-only plugins!
On Tue, Mar 24, 2015 at 9:42 AM, Ian Clelland iclell...@chromium.org
wrote:
We should definitely do that -- and I think we should release them
simultaneously with cordova-app-hello-world, since it now references
cordova-plugin-whitelist by that name
I'd like to start a vote thread for both plugins. I'm thinking they will
only be published to npm and dist (no CPR).
Thoughts?
