[
https://issues.apache.org/jira/browse/CB-13695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517631#comment-16517631
]
Raphael commented on CB-13695:
------------------------------
Since there were major changes to cordova-fetch lately, could you please test
if the issue persists on cordova@nightly?
When you do so, delete your node_modules, run with --verbose and make sure you
actually see output like the following:
{code:java}
fetch: Installing cordova-android@^7.0.0 to /tmp/tmp.4VQKXXz8Q2/cb-13797
Running command: npm install cordova-android@^7.0.0 --production --no-save
{code}
Otherwise cordova-fetch might be reusing already installed versions of your
dependencies.
> cordova-fetch: ignores npm registry
> -----------------------------------
>
> Key: CB-13695
> URL: https://issues.apache.org/jira/browse/CB-13695
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-fetch
> Affects Versions: cordova@8.0.0
> Reporter: Heiko
> Priority: Critical
>
> My situation:
> a build server that has no access to the internet.
> By to a local npm mirror.
> If i do at my build job:
> npm config set registry "http://my.local.server/repository/mirror.npm";
> npm install
> npm install cordova ionic npm --no-save
> cordova platform add ios --no-update-notifier
> i get:
> Using cordova-fetch for cordova-ios@4.5.3
> (node:391) UnhandledPromiseRejectionWarning: Unhandled promise rejection
> (rejection id: 1): Error: Cannot find module './index'
> (node:391) [DEP0018] DeprecationWarning: Unhandled promise rejections are
> deprecated. In the future, promise rejections that are not handled will
> terminate the Node.js process with a non-zero exit code.
> My work around for cordova 7 was to use: --nofetch
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
