You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Jan Piotrowski <pi...@gmail.com> on 2019/05/11 07:52:55 UTC
Plugins and Node.js versions
Currently our plugin CI uses the same version of Node.js as Tooling
and Platforms, until recently 4.2 and now 6.
But if I am not mistaken, our plugins do not contain any scripts that
are executed on the developer machine, only JavaScript files that are
run inside the app or native code. So it doesn't really matter what
node version is used to run our plugin CI tests as it doesn't run any
actual scripts (vs. with platforms, we have scripts that are actually
run by the developer).
Could we maybe just go to node 10 or 12 with our plugins right now?
This would give as quite some time until we have to update our CI
configuration again, and possibly also quicker installs and builds.
Best,
Jan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Plugins and Node.js versions
Posted by ra...@gmail.com.
👍
Jan Piotrowski <pi...@gmail.com> schrieb am Fr., 17. Mai 2019, 12:14:
> Additional thought:
> This means that it doesn't make sense to test plugins in multiple
> Node.js versions as well, the best and fastest is always ok for
> plugins, correct?
>
> -J
>
> Am Fr., 17. Mai 2019 um 07:49 Uhr schrieb Jesse <pu...@gmail.com>:
> >
> > Sounds good to me.
> > Faster CI is better CI
> >
> >
> > On Thu, May 16, 2019 at 2:16 PM Jan Piotrowski <pi...@gmail.com>
> wrote:
> >
> > > None of the plugins have a `hooks` directory or anything else that
> > > looks similar.
> > >
> > > Is anyone aware of any script in the plugin repositories that is
> > > executed on the developer side?
> > >
> > > Otherwise I think we should be good to define adding and dropping
> > > Node.js versions as non-breaking for plugins.
> > >
> > > Best,
> > > Jan
> > >
> > > Am Sa., 11. Mai 2019 um 10:49 Uhr schrieb <ra...@gmail.com>:
> > > >
> > > > Sounds like a good idea under the premise that our plugins really do
> not
> > > > contain any scripts that
> > > > are executed on the developer machine.
> > > >
> > > > But aren't there any core plugins that define hooks?
> > > >
> > > > Am Sa., 11. Mai 2019 um 10:03 Uhr schrieb Jan Piotrowski <
> > > > piotrowski@gmail.com>:
> > > >
> > > > > Currently our plugin CI uses the same version of Node.js as Tooling
> > > > > and Platforms, until recently 4.2 and now 6.
> > > > >
> > > > > But if I am not mistaken, our plugins do not contain any scripts
> that
> > > > > are executed on the developer machine, only JavaScript files that
> are
> > > > > run inside the app or native code. So it doesn't really matter what
> > > > > node version is used to run our plugin CI tests as it doesn't run
> any
> > > > > actual scripts (vs. with platforms, we have scripts that are
> actually
> > > > > run by the developer).
> > > > >
> > > > > Could we maybe just go to node 10 or 12 with our plugins right now?
> > > > >
> > > > > This would give as quite some time until we have to update our CI
> > > > > configuration again, and possibly also quicker installs and builds.
> > > > >
> > > > > Best,
> > > > > Jan
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > > >
> > > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Plugins and Node.js versions
Posted by Jan Piotrowski <pi...@gmail.com>.
Additional thought:
This means that it doesn't make sense to test plugins in multiple
Node.js versions as well, the best and fastest is always ok for
plugins, correct?
-J
Am Fr., 17. Mai 2019 um 07:49 Uhr schrieb Jesse <pu...@gmail.com>:
>
> Sounds good to me.
> Faster CI is better CI
>
>
> On Thu, May 16, 2019 at 2:16 PM Jan Piotrowski <pi...@gmail.com> wrote:
>
> > None of the plugins have a `hooks` directory or anything else that
> > looks similar.
> >
> > Is anyone aware of any script in the plugin repositories that is
> > executed on the developer side?
> >
> > Otherwise I think we should be good to define adding and dropping
> > Node.js versions as non-breaking for plugins.
> >
> > Best,
> > Jan
> >
> > Am Sa., 11. Mai 2019 um 10:49 Uhr schrieb <ra...@gmail.com>:
> > >
> > > Sounds like a good idea under the premise that our plugins really do not
> > > contain any scripts that
> > > are executed on the developer machine.
> > >
> > > But aren't there any core plugins that define hooks?
> > >
> > > Am Sa., 11. Mai 2019 um 10:03 Uhr schrieb Jan Piotrowski <
> > > piotrowski@gmail.com>:
> > >
> > > > Currently our plugin CI uses the same version of Node.js as Tooling
> > > > and Platforms, until recently 4.2 and now 6.
> > > >
> > > > But if I am not mistaken, our plugins do not contain any scripts that
> > > > are executed on the developer machine, only JavaScript files that are
> > > > run inside the app or native code. So it doesn't really matter what
> > > > node version is used to run our plugin CI tests as it doesn't run any
> > > > actual scripts (vs. with platforms, we have scripts that are actually
> > > > run by the developer).
> > > >
> > > > Could we maybe just go to node 10 or 12 with our plugins right now?
> > > >
> > > > This would give as quite some time until we have to update our CI
> > > > configuration again, and possibly also quicker installs and builds.
> > > >
> > > > Best,
> > > > Jan
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > > For additional commands, e-mail: dev-help@cordova.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Plugins and Node.js versions
Posted by Jesse <pu...@gmail.com>.
Sounds good to me.
Faster CI is better CI
On Thu, May 16, 2019 at 2:16 PM Jan Piotrowski <pi...@gmail.com> wrote:
> None of the plugins have a `hooks` directory or anything else that
> looks similar.
>
> Is anyone aware of any script in the plugin repositories that is
> executed on the developer side?
>
> Otherwise I think we should be good to define adding and dropping
> Node.js versions as non-breaking for plugins.
>
> Best,
> Jan
>
> Am Sa., 11. Mai 2019 um 10:49 Uhr schrieb <ra...@gmail.com>:
> >
> > Sounds like a good idea under the premise that our plugins really do not
> > contain any scripts that
> > are executed on the developer machine.
> >
> > But aren't there any core plugins that define hooks?
> >
> > Am Sa., 11. Mai 2019 um 10:03 Uhr schrieb Jan Piotrowski <
> > piotrowski@gmail.com>:
> >
> > > Currently our plugin CI uses the same version of Node.js as Tooling
> > > and Platforms, until recently 4.2 and now 6.
> > >
> > > But if I am not mistaken, our plugins do not contain any scripts that
> > > are executed on the developer machine, only JavaScript files that are
> > > run inside the app or native code. So it doesn't really matter what
> > > node version is used to run our plugin CI tests as it doesn't run any
> > > actual scripts (vs. with platforms, we have scripts that are actually
> > > run by the developer).
> > >
> > > Could we maybe just go to node 10 or 12 with our plugins right now?
> > >
> > > This would give as quite some time until we have to update our CI
> > > configuration again, and possibly also quicker installs and builds.
> > >
> > > Best,
> > > Jan
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > > For additional commands, e-mail: dev-help@cordova.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: Plugins and Node.js versions
Posted by Jan Piotrowski <pi...@gmail.com>.
None of the plugins have a `hooks` directory or anything else that
looks similar.
Is anyone aware of any script in the plugin repositories that is
executed on the developer side?
Otherwise I think we should be good to define adding and dropping
Node.js versions as non-breaking for plugins.
Best,
Jan
Am Sa., 11. Mai 2019 um 10:49 Uhr schrieb <ra...@gmail.com>:
>
> Sounds like a good idea under the premise that our plugins really do not
> contain any scripts that
> are executed on the developer machine.
>
> But aren't there any core plugins that define hooks?
>
> Am Sa., 11. Mai 2019 um 10:03 Uhr schrieb Jan Piotrowski <
> piotrowski@gmail.com>:
>
> > Currently our plugin CI uses the same version of Node.js as Tooling
> > and Platforms, until recently 4.2 and now 6.
> >
> > But if I am not mistaken, our plugins do not contain any scripts that
> > are executed on the developer machine, only JavaScript files that are
> > run inside the app or native code. So it doesn't really matter what
> > node version is used to run our plugin CI tests as it doesn't run any
> > actual scripts (vs. with platforms, we have scripts that are actually
> > run by the developer).
> >
> > Could we maybe just go to node 10 or 12 with our plugins right now?
> >
> > This would give as quite some time until we have to update our CI
> > configuration again, and possibly also quicker installs and builds.
> >
> > Best,
> > Jan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> > For additional commands, e-mail: dev-help@cordova.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: Plugins and Node.js versions
Posted by ra...@gmail.com.
Sounds like a good idea under the premise that our plugins really do not
contain any scripts that
are executed on the developer machine.
But aren't there any core plugins that define hooks?
Am Sa., 11. Mai 2019 um 10:03 Uhr schrieb Jan Piotrowski <
piotrowski@gmail.com>:
> Currently our plugin CI uses the same version of Node.js as Tooling
> and Platforms, until recently 4.2 and now 6.
>
> But if I am not mistaken, our plugins do not contain any scripts that
> are executed on the developer machine, only JavaScript files that are
> run inside the app or native code. So it doesn't really matter what
> node version is used to run our plugin CI tests as it doesn't run any
> actual scripts (vs. with platforms, we have scripts that are actually
> run by the developer).
>
> Could we maybe just go to node 10 or 12 with our plugins right now?
>
> This would give as quite some time until we have to update our CI
> configuration again, and possibly also quicker installs and builds.
>
> Best,
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>