I'm a fan of shipping dependencies shrink wrapped but as mentioned
this is not generally done at Apache. (Except for when it is like
Maven.)
I wonder if there's a bootstrap way we could look at? One less install
step, and assurance of a sane (or at least expected) runtime is nice.
On Wed, Jun
Those dependencies are, as I recently noted elsewhere, artificially high. I
think 0.8.6 or so is sufficient if we switch to using os.tmpDir() (the 0.8
name for it, and a synonym for the new, 0.10 name os.tmpdir()).
Braden
On Wed, Jun 19, 2013 at 5:28 PM, Filip Maj f...@adobe.com wrote:
Email: john.wa...@sap.com
Twitter: @johnwargo
-Original Message-
From: Bryan Higgins [mailto:br...@bryanhiggins.net]
Sent: Wednesday, June 19, 2013 3:22 PM
To: dev@cordova.apache.org
Subject: Re: BB10 bundling of node.js
So for Cordova 3.0 in general, users will be required to pre
, June 19, 2013 3:22 PM
To: dev@cordova.apache.org
Subject: Re: BB10 bundling of node.js
So for Cordova 3.0 in general, users will be required to pre-install a
minimum version of node globally?
We have had issues where upgrading node breaks stuff. I'd like to avoid
that and give users
I'd like to reopen the topic of bundling node js into the blackberry
platform.
I have personally gotten feedback from users of errors which were caused by
node version inconsistencies. We have since updated the check_req script to
test for the minimum version of node we require, but that is not
-1
I would rather we just use the system version of node which would be the
same version as the CLI. I can't think of any reason a specific platform
(aka BlackBerry) would need a special version of a common dependency.
Also I don't think you can bundle binaries in an apache release.
On Wed,
So for Cordova 3.0 in general, users will be required to pre-install a
minimum version of node globally?
We have had issues where upgrading node breaks stuff. I'd like to avoid
that and give users flexibility with their own system configuration.
On Wed, Jun 19, 2013 at 3:09 PM, Gord Tanner
I would expect they would have a supported node version when they type:
npm install cordova
which would do any version checks in the package.json [1] for supported
node versions
[1] -
https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=blob_plain;f=package.json;hb=HEAD
On Wed, Jun 19,
For 3.0 will there still be a ZIP file released by Apache? Will the
instructions be download the latest version of node then run npm install
-g path to cordova-cli?
My assumption was the individual project templates will continue to work
independently of CLI.
Also, keep in mind that CLI invokes
Still a -1, cordova (and all it's projects) should use the globally
installed version of node.
If someone needs multiple versions of node the should probably use nvm [1]
to manage it. IMHO this is a user problem and not something we should
magically solve via bundled copies of node or hardcoded
Plugman and cordova-cli both require a minimum 0.9.9 node.
See the engines and engineStrict flags in package.json for the two
repos. engineStrict when set to true will force npm to make sure the
user's version of node adheres to what is listed under the engines prop.
On 6/19/13 1:15 PM, Gord
11 matches
Mail list logo
