SAP / cloud-mta-build-tool

Multi-Target Application (MTA) build tool for Cloud Applications https://sap.github.io/cloud-mta-build-tool
Apache License 2.0
136 stars 56 forks source link

MBT version 1.2.25 is not working after installation under proxy #1075

Open tavnabisoft opened 10 months ago

tavnabisoft commented 10 months ago

MBT version 1.2.25 is not working after installation under corporate proxy.

After you run npm i mbt@1.2.25, and then run any command of mbt like npx mbt --version, it does nothing. We're running under corporate proxy, environment variables like HTTP_PROXY and HTTPS_PROXY are set properly with required authorization. It worked well with all previous patch versions of mbt (1.2.24, 1.2.23, ...) in same environment under corporate proxy. I've checked the mbt package in node_modules and found that unpacked_bin folder is empty for 1.2.25, however it is filled with mbt.exe executable for all previous versions. I noticed from source code, that the way how package is downloaded from github has been changed. So I guess this is the root cause of the issue.

Please provide the following info:

Steps to Reproduce:

  1. Run npm i mbt@1.2.25 under corporate proxy
  2. Run npx mbt --version - there is no expected output
  3. Check node_modules/mbt/unpacked_bin folder - it is empty
zouyi100 commented 9 months ago

Yes, i have the same issue.

rd-andreas-rosemeier commented 9 months ago

We have the same issue with our corporate proxy.

ThomasSchilling85 commented 8 months ago

I have also the same issue.

powerdan commented 5 months ago

+1 here - have fixed it now to 1.2.24 and hoping, this will be fixed someday...

powerdan commented 5 months ago

I guess the issue is, that https://github.com/SAP/cloud-mta-build-tool/blob/01c96e02f30d6ebde1eaf26fc4346bb7f7e55e43/install.js introduced in 1.2.25 does not take care of the proxy.

sadly i am not enough into nodejs to fix this...

cccampos123 commented 5 months ago

I fixed this problem with a workaround using 1.2.27: Coping all files from C:\ProgramData\nvm (windows 10) to my new machine with windows 11.

sp00kyDD commented 3 months ago

same issue here