Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 16 Nov 2017 12:24:00 +0000 (UTC)
From: "Lukas Plachy (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.13115958.1509722968000.255402.1510835040313@Atlassian.JIRA>
In-Reply-To: <JIRA.13115958.1509722968000@Atlassian.JIRA>
References: <JIRA.13115958.1509722968000@Atlassian.JIRA> <JIRA.13115958.1509722968268@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (CB-13536) cordova being called from
 "quasar wrap" not working - cordova-realted error when not installed in
 default directory: Could not install from (path_of_nodejs_modules) as it
 does not contain a package.json file
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Nov 2017 12:24:06 -0000


    [ https://issues.apache.org/jira/browse/CB-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255204#comment-16255204 ] 

Lukas Plachy edited comment on CB-13536 at 11/16/17 12:23 PM:
--------------------------------------------------------------

Well, well, well ... so we have the intermediate cause of this problem: When installed in default paths, the whole thing works like a charm. See attached screenshots ([^cordova_create_over_nvm_std_dirs.png] and [^cordova_create_direct_MSI_install_std_dirs.png]), however they do not bring any additional information.
So let me make an 'expert guess', just only as a small hint from my (bad) experience: The error message string construction in the source code uses a different 'base_path' variable (I do not know the exact name of the variable, Im just guessing there must be such one) than the real command trying to copy the file(s), which definitely uses some other construction or a different 'base_path' variable.

That is for me currently the final state of this ticket, Im afraid I cant help you anymore. Of course I'll try to find some workaround and if succesfull, then I'll append it here (and report to our sysadmins so that they are aware of the risk of Roaming profile bloating out of controll), but the solution itself remains most probably in the code, unless Im missing something else.

Thanks for cooperation and help so far and many thanks for the tip with the default directories. Should I be able to help you with anything else or if any detailed information shall be needed, do not hesitate to contact me through this ticket or directly through my profile. 

>>> Knowledge base addendum when trying to work with direct install from MSI and not the using nvm:
FOR ANYONE to whom it may concern when facing the issue (on Windows) that after 'npm install -g anything' the module being installed (if a CLI present) does not work in CLI, please note following:
- the '-g' means, that the new packages of nodejs will be installed not into the nodejs directory (default C:\Program Files\nodejs) but into the 'C:\Users\%USERNAME%\AppData\Roaming\npm' directory.
- the problem above is overriden (probably during 'npm install -g npm', but that's also only my guess) in such a way, that the C:\Users\.....\npm is appended into the %PATH% variable, however one has to restart also the cmd.exe (commandline console in windows) in order to load and use the newly altered %PATH% variable
- if you need to install some module "globally" but into a custom directory, then it might be done by 'cd my_nodejs_directory' and do a non-global 'npm install something', however this may result into unexpected behaviour, if the module in question does not expect this (such as the case of this ticket)


was (Author: rheingold):
Well, well, well ... so we have the intermediate cause of this problem: When installed in default paths, the whole thing works like a charm. See attached screenshots ([^cordova_create_over_nvm_std_dirs.png] and [^cordova_create_direct_MSI_install_std_dirs.png]), however they do not bring any addtitional information.
So let me make an 'expert guess', just only as a small hint from my (bad) experience: The error message string construction in the source code uses a different 'base_path' variable (I do not know the exact name of the variable, Im just guessing there must be such one) than the real command trying to copy the file(s), which definitely uses some other construction or a different 'base_path' variable.

That is for me currently the final state of this ticket, Im afraid I cant help you anymore. Of course I'll try to find some workaround and if succesfull, then I'll append it here (and report to our sysadmins so that they are aware of the risk of Roaming profile bloating out of controll), but the solution itself remains most probably in the code, unless Im missing something else.

Thanks for cooperation and help so far and many thanks for the tip with the default directories. Should I be able to help you with anything else or if any detailed information shall be needed, do not hesitate to contact me through this ticket or directly through my profile. 

>>> Knowledge base addendum when trying to work with direct install from MSI and not the using nvm:
FOR ANYONE to whom it may concern when facing the issue (on Windows) that after 'npm install -g anything' the module being installed (if a CLI present) does not work in CLI, please note following:
- the '-g' means, that the new packages of nodejs will be installed not into the nodejs directory (default C:\Program Files\nodejs) but into the 'C:\Users\%USERNAME%\AppData\Roaming\npm' directory.
- the problem above is overriden (probably during 'npm install -g npm', but that's also only my guess) in such a way, that the C:\Users\.....\npm is appended into the %PATH% variable, however one has to restart also the cmd.exe (commandline console in windows) in order to load and use the newly altered %PATH% variable
- if you need to install some module "globally" but into a custom directory, then it might be done by 'cd my_nodejs_directory' and do a non-global 'npm install something', however this may result into unexpected behaviour, if the module in question does not expect this (such as the case of this ticket)

> cordova being called from "quasar wrap" not working - cordova-realted error when not installed in default directory: Could not install from (path_of_nodejs_modules) as it does not contain a package.json file
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CB-13536
>                 URL: https://issues.apache.org/jira/browse/CB-13536
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-app-hello-world, cordova-cli
>            Reporter: Lukas Plachy
>         Attachments: 2017-11-03T12_42_43_016Z-debug_anonymized.log, 2017-11-14T14_08_29_042Z-debug.log, cordova_create_cordova.png, cordova_create_direct_MSI_install_std_dirs.png, cordova_create_on_empty.png, cordova_create_over_nvm_std_dirs.png, cordova_wrap_fail.png, nvm_cordova_create.png, nvm_install.png
>
>
> Hi, anybody an idea, whats wrong here (see attached image), before I'll have to make a deepdive into the sources? Such error does not help when doing first hands-on!
> Note: has been reported to and rejected by quasar as not quasar-related.
> Thanks
> [^cordova_wrap_fail.png]


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org