shankari edited a comment on issue #87: URL: https://github.com/apache/cordova-fetch/issues/87#issuecomment-658400946
Ok, so I poked around this some more, and I know the reason behind the difference in `superspawn` behavior. After adding log statements to all instances of superspawn, it looks like this is difference is due to the differences in the versions of superspawn included in the project. ``` $ find node_modules -name \*superspawn.js node_modules/cordova/node_modules/cordova-common/src/superspawn.js node_modules/cordova-common/src/superspawn.js node_modules/cordova-create/node_modules/cordova-common/src/superspawn.js node_modules/cordova-fetch/node_modules/cordova-common/src/superspawn.js node_modules/cordova-lib/node_modules/cordova-common/src/superspawn.js node_modules/phonegap/node_modules/cordova-common/src/superspawn.js node_modules/phonegap/node_modules/cordova-create/node_modules/cordova-common/src/superspawn.js ``` While using node directly, we use `node_modules/cordova-common/src/superspawn.js`, while using `plugin add`, we use `node_modules/cordova-fetch/node_modules/cordova-common/src/superspawn.js`. The two versions are different, although I cannot see which of the differences lead to this difference in behavior. [not_working_to_working.diff.gz](https://github.com/apache/cordova-fetch/files/4921302/not_working_to_working.diff.gz) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
