-
Notifications
You must be signed in to change notification settings - Fork 61
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
Comments
Yes, i have the same issue. |
We have the same issue with our corporate proxy. |
I have also the same issue. |
+1 here - have fixed it now to 1.2.24 and hoping, this will be fixed someday... |
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... |
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. |
same issue here |
MBT version
1.2.25
is not working after installation under corporate proxy.After you run
npm i [email protected]
, and then run any command of mbt likenpx mbt --version
, it does nothing. We're running under corporate proxy, environment variables likeHTTP_PROXY
andHTTPS_PROXY
are set properly with required authorization. It worked well with all previous patch versions ofmbt
(1.2.24
,1.2.23
, ...) in same environment under corporate proxy. I've checked thembt
package innode_modules
and found thatunpacked_bin
folder is empty for1.2.25
, however it is filled withmbt.exe
executable for all previous versions. I noticed from source code, that the way how package is downloaded fromgithub
has been changed. So I guess this is the root cause of the issue.Please provide the following info:
1.2.25
Windows 11
Steps to Reproduce:
npm i [email protected]
under corporate proxynpx mbt --version
- there is no expected outputnode_modules/mbt/unpacked_bin
folder - it is emptyThe text was updated successfully, but these errors were encountered: