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 <[email protected]> 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: [email protected] [mailto:[email protected]] On Behalf Of > Darryl Pogue > Sent: Thursday, January 21, 2016 11:35 AM > To: [email protected] > 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 <[email protected]> wrote: > > YES YES YES! Please cordova_plugins.js is killing me. > > > > On Wed, Jan 20, 2016 at 4:10 PM Nikhil Khandelwal > > <[email protected]> > > 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: [email protected] > For additional commands, e-mail: [email protected] > >
