lgtm!
On Mon, May 19, 2014 at 3:49 PM, Marcel Kinard wrote:
> Here’s my proposal: https://github.com/apache/cordova-docs/pull/205
>
> Comments can go in the pull request.
Here’s my proposal: https://github.com/apache/cordova-docs/pull/205
Comments can go in the pull request.
>
> If we start telling devs how to configure their machines we might as well
> get into telling
> developers how to structure, test, and otherwise architect their apps.
But didn't we basically just do that with the Next Steps guide?
We didn't say explicitly say "you have to do it like X" - we p
I didn’t expect this topic to draw this much discussion.
I’m totally in agreement on "not fail by default”.
On May 12, 2014, at 11:51 PM, Ally Ogilvie wrote:
> However some simple text + links (based on [1]) such as this would do the
> trick no?
>
> 2. Install the Cordova utility.
> `npm inst
npm install! you can then call via npm scripts [1]. I have a project going
right now where I put all the automations in there. clean.
npm run ios === "scripts":{ "ios":"node node_modules/cordova/bin/cordova
run ios"}
On Tue, May 13, 2014 at 5:10 AM, Michal Mocny wrote:
> Tommy, how do you inst
I appreciate that everyone cares about the user's installation experience,
but it's also a little nuts that we're 16 message deep into the discussion
of installing a npm module. Like Brian mentioned, this isn't directly a
problem of Apache Cordova.
Let's break it down from a typical user's perspec
Yeah... What Brian said... But of course there is currently a chicken/egg
problem in that you need a Cordova installed somewhere to create the
project in the first place.
On 14 May 2014 02:18, "Brian LeRoux" wrote:
> npm install! you can then call via npm scripts [1]. I have a project going
> rig
Tommy, how do you install locally?
Specifically, do you install cordova inside a workspace, and if so, how do
you create that workspace first?
-Michal
On Mon, May 12, 2014 at 4:47 PM, Tommy Williams wrote:
> Just as an aside, I go the other way.. I install Cordova locally. This way
> I can ha
"How do I install Cordova?" is a problem that we should address, I think.
That said, broken by default is no good, and if someone has taken the extra
step to learn to use nvm, then they are probably fine to know that they
don't need sudo.
Installing locally is definitely still a path we could exp
Indeed. Although "sans sudo on npm install", we cannot hold the hand of the
developer during throughout the entirety use of npm on their machine.
However some simple text + links (based on [1]) such as this would do the
trick no?
2. Install the Cordova utility.
`npm install cordova`
Pointers:
*I
TLDR (as I understand it) - if you use nvm to install node, then you don't
need sudo. If you use Node's installer, than you do need sudo.
If you run on Windows, you don't need sudo.
On Mon, May 12, 2014 at 1:34 PM, Wargo, John wrote:
> I chatted with Fil about this in the pre-3 days and it was
Just as an aside, I go the other way.. I install Cordova locally. This way
I can have different versions of Cordova for different apps. I just use a
build tool (npm run or grunt etc) to call the local cordova .
Maybe we should revisit the grunt-style split between the global
cordova-cli and a loca
Once again, however, this is not a problem for Cordova to solve but rather
a part of the journey for the developer to undertake. If we start telling
devs how to configure their machines we might as well get into telling
developers how to structure, test, and otherwise architect their apps.
On Mon
You cannot install a module globally with a default install of Node. This
isn't really a Cordova issue but one of taste. Some people like to isolate
their systems and not install modules globally. Indeed, this is probably a
good practice. We could point the way in the docs but we do not want to
cha
I chatted with Fil about this in the pre-3 days and it was a requirement at the
time. Have things changed to the point where it works without it? Every time
I've tried to do it without sudo on Macintosh it fails.
-Original Message-
From: Marcel Kinard [mailto:cmarc...@gmail.com]
Sent:
Shazron wrote:
>The premise here is npm running sudo is dangerous. Here's what it does
>with
>that power:
>https://github.com/npm/npm/issues/294
>
>Note that the issue was filed and closed _after_ this article was written,
>so the article is actually stale:
>http://howtonode.org/introduction-to-npm
Marcel Kinard wrote:
>I'm not a Node.js expert, but the Linux person inside me says that using
>sudo to install and run things ought to be avoided if possible.
The Unix/Windows person in me is opposed to sudo, but I thought we had
covered most of the bases already, if we've missed places, please +
The premise here is npm running sudo is dangerous. Here's what it does with
that power:
https://github.com/npm/npm/issues/294
Note that the issue was filed and closed _after_ this article was written,
so the article is actually stale:
http://howtonode.org/introduction-to-npm
In my opinion, sudo i
I object. This does not solve a problem Cordova has set out to solve but
this does make installation unnecessarily harder. Linking those docs for
those whom want to level up their Node, and shell, acumen seems reasonable.
I'm not a Node.js expert, but the Linux person inside me says that using
sudo
+1
On Mon, May 12, 2014 at 12:38 AM, Don Coleman wrote:
> +1
> On May 11, 2014 6:37 AM, "Marcel Kinard" wrote:
>
> > I'm not a Node.js expert, but the Linux person inside me says that using
> > sudo to install and run things ought to be avoided if possible.
> >
> > Would there be objection if
+1
On May 11, 2014 6:37 AM, "Marcel Kinard" wrote:
> I'm not a Node.js expert, but the Linux person inside me says that using
> sudo to install and run things ought to be avoided if possible.
>
> Would there be objection if I changed cordova-docs to omit sudo from the
> npm install commands? And
21 matches
Mail list logo
