You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Nikhil Khandelwal <ni...@microsoft.com> on 2016/01/21 01:10:19 UTC
--browserify workflow status?
Where are we with --browserify support? From what I can see, most or all the work has been completed:
https://issues.apache.org/jira/browse/CB-8801
Should it move out of experimental now?[1]
It will help to document it and perhaps blog about its benefits as opposed to the current default workflow.
[1] https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
Thanks,
Nikhil
RE: --browserify workflow status?
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
Thanks, Steve for taking up on writing the blog post. It would be great to use that to drive some usage and feedback loop. Also, we might want to do JIRA triage of related issues to ensure that it does not result in any regressions. I took a quick look and most of it is not relevant currently [1]. Though CB-9967 might be a good one to fix.
I believe one of the advantages of browserify is that it results in lesser file loads - while this is mildly beneficial for local apps, it's perhaps a big deal for remote hosted cordova apps. Are there any downsides to using browserify?
Also, can a user reference arbitrary browserifiable[2] supported js libraries from node_modules in their cordova app with this. Docs and some walkthrough would be useful here. On a similar note, with this could a plugin add a reference to a nodejs module in its code? Of course, in that case, the plugin will *require* browserify workflow to function.
[1] https://issues.apache.org/jira/browse/CB-9967?jql=project%20%3D%20CB%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20text%20~%20browserify%20ORDER%20BY%20created%20DESC
[2] http://browserifysearch.org/
Thanks,
Nikhil
-----Original Message-----
From: Steven Gill [mailto:stevengill97@gmail.com]
Sent: Thursday, January 21, 2016 4:14 PM
To: dev@cordova.apache.org
Subject: Re: --browserify workflow status?
Should we set a rough goal/timeline on when to make this default? Cordova 6.1.0? Put the non browserify workflow behind a --no-browserify flag.
I'll plan to write a blog post and put it up for review week after PGDAY.
On Thu, Jan 21, 2016 at 1:19 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> Great! Looks like we just need to update the help text then. I sent a
> PR for this: https://github.com/apache/cordova-cli/pull/231
>
> Anyone wants to talk about the merits of using the browserify workflow?
> Our blog might be a good place for that.
>
> -Nikhil
>
> -----Original Message-----
> From: dvpdiner2@gmail.com [mailto:dvpdiner2@gmail.com] On Behalf Of
> Darryl Pogue
> Sent: Thursday, January 21, 2016 11:35 AM
> To: dev@cordova.apache.org
> Subject: Re: --browserify workflow status?
>
> I've been using the --browserify flag for several months and it's been
> working great
>
> On 21 January 2016 at 11:02, Anis KADRI <an...@gmail.com> wrote:
> > YES YES YES! Please cordova_plugins.js is killing me.
> >
> > On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal
> > <ni...@microsoft.com>
> > wrote:
> >
> >> Where are we with --browserify support? From what I can see, most
> >> or all the work has been completed:
> >>
> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fis
> >> su
> >> es.apache.org%2fjira%2fbrowse%2fCB-8801&data=01%7c01%7cnikhilkh%40m
> >> ic
> >> rosoft.com%7c530238f80e1c41e776d308d32299e90a%7c72f988bf86f141af91a
> >> b2
> >> d7cd011db47%7c1&sdata=p1p5LVB7ywO29s8%2bmU%2fmhaiN9guzvp5qHDqroc2p1
> >> QU
> >> %3d
> >>
> >> Should it move out of experimental now?[1]
> >>
> >> It will help to document it and perhaps blog about its benefits as
> >> opposed to the current default workflow.
> >>
> >> [1]
> >> https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
> >>
> >> Thanks,
> >> Nikhil
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
Re: --browserify workflow status?
Posted by Steven Gill <st...@gmail.com>.
Should we set a rough goal/timeline on when to make this default? Cordova
6.1.0? Put the non browserify workflow behind a --no-browserify flag.
I'll plan to write a blog post and put it up for review week after PGDAY.
On Thu, Jan 21, 2016 at 1:19 PM, Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> Great! Looks like we just need to update the help text then. I sent a PR
> for this: https://github.com/apache/cordova-cli/pull/231
>
> Anyone wants to talk about the merits of using the browserify workflow?
> Our blog might be a good place for that.
>
> -Nikhil
>
> -----Original Message-----
> From: dvpdiner2@gmail.com [mailto:dvpdiner2@gmail.com] On Behalf Of
> Darryl Pogue
> Sent: Thursday, January 21, 2016 11:35 AM
> To: dev@cordova.apache.org
> Subject: Re: --browserify workflow status?
>
> I've been using the --browserify flag for several months and it's been
> working great
>
> On 21 January 2016 at 11:02, Anis KADRI <an...@gmail.com> wrote:
> > YES YES YES! Please cordova_plugins.js is killing me.
> >
> > On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal
> > <ni...@microsoft.com>
> > wrote:
> >
> >> Where are we with --browserify support? From what I can see, most or
> >> all the work has been completed:
> >>
> >> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissu
> >> es.apache.org%2fjira%2fbrowse%2fCB-8801&data=01%7c01%7cnikhilkh%40mic
> >> rosoft.com%7c530238f80e1c41e776d308d32299e90a%7c72f988bf86f141af91ab2
> >> d7cd011db47%7c1&sdata=p1p5LVB7ywO29s8%2bmU%2fmhaiN9guzvp5qHDqroc2p1QU
> >> %3d
> >>
> >> Should it move out of experimental now?[1]
> >>
> >> It will help to document it and perhaps blog about its benefits as
> >> opposed to the current default workflow.
> >>
> >> [1]
> >> https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
> >>
> >> Thanks,
> >> Nikhil
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
> For additional commands, e-mail: dev-help@cordova.apache.org
>
>
RE: --browserify workflow status?
Posted by Nikhil Khandelwal <ni...@microsoft.com>.
Great! Looks like we just need to update the help text then. I sent a PR for this: https://github.com/apache/cordova-cli/pull/231
Anyone wants to talk about the merits of using the browserify workflow? Our blog might be a good place for that.
-Nikhil
-----Original Message-----
From: dvpdiner2@gmail.com [mailto:dvpdiner2@gmail.com] On Behalf Of Darryl Pogue
Sent: Thursday, January 21, 2016 11:35 AM
To: dev@cordova.apache.org
Subject: Re: --browserify workflow status?
I've been using the --browserify flag for several months and it's been working great
On 21 January 2016 at 11:02, Anis KADRI <an...@gmail.com> wrote:
> YES YES YES! Please cordova_plugins.js is killing me.
>
> On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal
> <ni...@microsoft.com>
> wrote:
>
>> Where are we with --browserify support? From what I can see, most or
>> all the work has been completed:
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fissu
>> es.apache.org%2fjira%2fbrowse%2fCB-8801&data=01%7c01%7cnikhilkh%40mic
>> rosoft.com%7c530238f80e1c41e776d308d32299e90a%7c72f988bf86f141af91ab2
>> d7cd011db47%7c1&sdata=p1p5LVB7ywO29s8%2bmU%2fmhaiN9guzvp5qHDqroc2p1QU
>> %3d
>>
>> Should it move out of experimental now?[1]
>>
>> It will help to document it and perhaps blog about its benefits as
>> opposed to the current default workflow.
>>
>> [1]
>> https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
>>
>> Thanks,
>> Nikhil
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: --browserify workflow status?
Posted by Darryl Pogue <da...@dpogue.ca>.
I've been using the --browserify flag for several months and it's been
working great
On 21 January 2016 at 11:02, Anis KADRI <an...@gmail.com> wrote:
> YES YES YES! Please cordova_plugins.js is killing me.
>
> On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal <ni...@microsoft.com>
> wrote:
>
>> Where are we with --browserify support? From what I can see, most or all
>> the work has been completed:
>>
>> https://issues.apache.org/jira/browse/CB-8801
>>
>> Should it move out of experimental now?[1]
>>
>> It will help to document it and perhaps blog about its benefits as opposed
>> to the current default workflow.
>>
>> [1] https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
>>
>> Thanks,
>> Nikhil
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org
Re: --browserify workflow status?
Posted by Anis KADRI <an...@gmail.com>.
YES YES YES! Please cordova_plugins.js is killing me.
On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal <ni...@microsoft.com>
wrote:
> Where are we with --browserify support? From what I can see, most or all
> the work has been completed:
>
> https://issues.apache.org/jira/browse/CB-8801
>
> Should it move out of experimental now?[1]
>
> It will help to document it and perhaps blog about its benefits as opposed
> to the current default workflow.
>
> [1] https://github.com/apache/cordova-cli/blob/master/doc/build.txt#L27
>
> Thanks,
> Nikhil
>