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

Error when clicking "Create MTA Module from Template" in VS Code #455

Open
demoll-sap opened this issue Nov 14, 2023 · 7 comments
Open

Error when clicking "Create MTA Module from Template" in VS Code #455

demoll-sap opened this issue Nov 14, 2023 · 7 comments

Comments

@demoll-sap
Copy link

Hello,

I'm stuck on this step of the install: MTA tool to add MTA modules.
Ran npm install -g mta but still encountered the below error:

Screenshot 2023-11-14 112635

Could someone please explain how to install this VS Code extension?

@sammok83
Copy link

I'm getting the same error too

@memgavdilabs
Copy link

Has anyone been successful in using this ?

@rakesh290394
Copy link

first i have installed

@ignipae
Copy link

ignipae commented May 15, 2024

This is a huge issue for windows users. Is there any known workaround?

@aelox
Copy link

aelox commented May 19, 2024

My personal solution (on windows 10):

  1. Install the Cloud-MTA-Tool by npm install -g mta.
  2. By npm list -g find the path of your global node modules.
  3. As a privileged user, copy the exe file C:\path\to\globel\modules\node_modules\mta\unpacked_bin\mta.exe to the %windir% folder (mostly to C:\Windows) or to a folder where the PATH environment variable points to.
  4. Check with where mta that the copied mta.exe file is the first executable that the system meets.
  5. Now install the vscode-mta-tools tools in visual studio code ... best within a bash shell as retrieved from https://git-scm.com/ by issuing git clone https://github.com/SAP/vscode-mta-tools and cd vscode-mta-tools, replacing the lines in package.json containing "vsce": "1.96.1" and "vscode-test": "1.5.2" by "@vscode/vsce": "^2" resp. "@vscode/test-electron": "^2", running npm audit fix --force, npm update --package-lock-only and then npm run ci. All tests should now pass (possibly you have to put %ProgramFiles%\Git\bin into the PATH environment variable after %ProgramFiles%\Git\cmd.

But what is it for? At the end, the above mention error message does no longer popup, but the extension claims: "Could not find any generators." :-(

@kiransterling
Copy link

I am getting the same error

1 similar comment
@I554722
Copy link

I554722 commented Jul 8, 2024

I am getting the same error

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

8 participants