[Bug]: Windows node.js needs extra shim for npm.cmd

[AlanBarber]

Description

When running an asp.net core app that makes use of the SpaProxyLaunch tooling instead of directly calling npm it calls a npm.cmd (which is part of every node install on windows).

https://github.com/dotnet/aspnetcore/blob/07f13c1553ace296f26236eeab6f5e5ec3bd6e9a/src/Middleware/Spa/SpaProxy/src/SpaProxyLaunchManager.cs#L178

so we need a new npm.cmd shim in the shim folder...

i'm not sure if you want to redirect it to the actual npm.cmd

in testing I created a npm.cmd in the shim folder with this code below and just had it call the npm.exe shim and everything seemed to run fine for my project.

@echo off
"%~dp0npm.exe" %*

Steps to Reproduce

see description

Expected Behavior

see description

Actual Behavior

see description

Operating System

Windows

dtvem Version

0.5.1

Go Version (if building from source)

No response

Which runtime is affected?

Node.js

Error Messages / Logs

Configuration

Additional Context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[CalvinAllen]

Hmm, that's interesting. I think the cmd redirect to the shim exe is probably the easiest route, but I'll need to figure out how to create those on the fly with reshim.