Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tavnabisoft opened this issue Sep 20, 2023 · 7 comments
Open

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

tavnabisoft opened this issue Sep 20, 2023 · 7 comments

Comments

@tavnabisoft
Copy link

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:

  • MBT Version: 1.2.25
  • OS Version: Windows 11

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
Copy link

Yes, i have the same issue.

@rd-andreas-rosemeier
Copy link

We have the same issue with our corporate proxy.

@ThomasSchilling85
Copy link

I have also the same issue.

@powerdan
Copy link

powerdan commented Feb 1, 2024

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

@powerdan
Copy link

powerdan commented Feb 5, 2024

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
Copy link

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
Copy link

same issue here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants