: Building cordova.js on first build
+1
On Thu, May 28, 2015 at 6:32 PM, Steven Gill stevengil...@gmail.com
wrote:
Right now, only the --browserify way does cordova.js generation in
the
cli.
--browserify is currently designed to work with the CLI. I don't
think it is worth it to add
] On Behalf Of
Brian LeRoux
Sent: Friday, May 29, 2015 5:55 AM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
+1
On Thu, May 28, 2015 at 6:32 PM, Steven Gill stevengil...@gmail.com
wrote:
Right now, only the --browserify way does cordova.js generation
[mailto:brian.ler...@gmail.com] On Behalf Of Brian
LeRoux
Sent: Friday, May 29, 2015 5:55 AM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
+1
On Thu, May 28, 2015 at 6:32 PM, Steven Gill stevengil...@gmail.com wrote:
Right now, only the --browserify way does cordova.js generation
though 4.0.0
is already out there.
Thanks,
Nikhil
-Original Message-
From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf
Of Brian LeRoux
Sent: Friday, May 29, 2015 5:55 AM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
+1
On Thu
-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, May 26, 2015 5:40 PM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
npm linking is suggested when testing platform specific JS changes.
cordova-coho's prepare-release-branch command
cordova.js on first build
npm linking is suggested when testing platform specific JS changes.
cordova-coho's prepare-release-branch command will generate cordova.js
and
move it over to the platform, as well as other things, when doing a
release. It might be worth breaking out
@cordova.apache.org
Subject: Re: Building cordova.js on first build
npm linking is suggested when testing platform specific JS changes.
cordova-coho's prepare-release-branch command will generate cordova.js and
move it over to the platform, as well as other things, when doing a
release. It might
If people are into it, I can handle this one as I am very familiar with the
code base since I just did it for the browserify workflow.
On Tue, May 26, 2015 at 4:15 PM, Steven Gill stevengil...@gmail.com wrote:
Hey Murat,
By two files you mean cordova-js-src and www\cordova.js I assume. The
the user has but otherwise the file is static.
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, May 26, 2015 5:10 PM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
If people are into it, I can handle this one as I am very
the file is static.
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, May 26, 2015 5:10 PM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
If people are into it, I can handle this one as I am very familiar with
the code
I think this would be a valuable addition to coho.
+1
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Tuesday, May 26, 2015 5:40 PM
To: dev@cordova.apache.org
Subject: Re: Building cordova.js on first build
npm linking is suggested when testing platform
Hey there,
I've a quick question. Now that every platform comes with cordova-js-src should
we remove the www\cordova.js from platform repos?
I think it's a better idea to compile cordova.js on first build if it's
missing. This way we don't have to update two files when working on platform js.
Hey Murat,
By two files you mean cordova-js-src and www\cordova.js I assume. The
www\cordova.js file is generated and updated on each release of the
platform. It will use cordova-js-src to build it when available (instead of
legacy-exe version)
Problem with removing www\cordova.js and building
13 matches
Mail list logo
