Cannot start a debug session on a remote connection on Amazon Linux

[ashishchandr70]

• VSCode Version: 1.49.2
• OS Version: Ubuntu 18.04 is the host machine OS. Connecting using VS Code to remote ssh session on Amazon Linux

Steps to Reproduce:

1. In my case, open VS Code on my Ubuntu machine
2. Connect to AWS Amazon Linux instance
3. Run debugger using launch.json
4. I get the 127 error message first. I hit debug anyway and then
5. The error on node not found pops up

Notes:

The exact error is

> Executing task: tsc -p /usr/local/src/test_deploy/tsconfig.json <

/bin/bash: tsc: command not found
The terminal process "/bin/bash '-c', 'tsc -p /usr/local/src/test_deploy/tsconfig.json'" failed to launch (exit code: 127).

Terminal will be reused by tasks, press any key to close it.

If I open a bash terminal on the remote Amazon machine and type the tsc -p /usr/local/src/test_deploy/tsconfig.json command, it works without any issues.

Here is the npm config ls -l

; cli configs
long = true
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/6.14.8 node/v14.13.1 linux x64"

; userconfig /home/ec2-user/.npmrc
HOME = "/home/ec2-user"
cwd = "/usr/local/src/cryptofights_eb_deploy"
node_bin_location = "/home/ec2-user/.nvm/versions/node/v14.13.1/bin/node"

; default values
access = null
allow-same-version = false
also = null
always-auth = false
audit = true
audit-level = "low"
auth-type = "legacy"
before = null
bin-links = true
browser = null
ca = null
cache = "/home/ec2-user/.npm"
cache-lock-retries = 10
cache-lock-stale = 60000
cache-lock-wait = 10000
cache-max = null
cache-min = 10
cafile = undefined
cert = null
cidr = null
color = true
commit-hooks = true
depth = null
description = true
dev = false
dry-run = false
editor = "vi"
engine-strict = false
fetch-retries = 2
fetch-retry-factor = 10
fetch-retry-maxtimeout = 60000
fetch-retry-mintimeout = 10000
force = false
format-package-lock = true
fund = true
git = "git"
git-tag-version = true
global = false
global-style = false
globalconfig = "/home/ec2-user/.nvm/versions/node/v14.13.1/etc/npmrc"
globalignorefile = "/home/ec2-user/.nvm/versions/node/v14.13.1/etc/npmignore"
group = 1000
ham-it-up = false
heading = "npm"
https-proxy = null
if-present = false
ignore-prepublish = false
ignore-scripts = false
init-author-email = ""
init-author-name = ""
init-author-url = ""
init-license = "ISC"
init-module = "/home/ec2-user/.npm-init.js"
init-version = "1.0.0"
json = false
key = null
legacy-bundling = false
link = false
local-address = undefined
loglevel = "notice"
logs-max = 10
; long = false (overridden)
maxsockets = 50
message = "%s"
; metrics-registry = null (overridden)
node-options = null
node-version = "14.13.1"
noproxy = null
offline = false
onload-script = null
only = null
optional = true
otp = null
package-lock = true
package-lock-only = false
parseable = false
prefer-offline = false
prefer-online = false
prefix = "/home/ec2-user/.nvm/versions/node/v14.13.1"
preid = ""
production = false
progress = true
proxy = null
read-only = false
rebuild-bundle = true
registry = "https://registry.npmjs.org/"
rollback = true
save = true
save-bundle = false
save-dev = false
save-exact = false
save-optional = false
save-prefix = "^"
save-prod = false
scope = ""
script-shell = null
scripts-prepend-node-path = "warn-only"
searchexclude = null
searchlimit = 20
searchopts = ""
searchstaleness = 900
send-metrics = false
shell = "/bin/bash"
shrinkwrap = true
sign-git-commit = false
sign-git-tag = false
sso-poll-frequency = 500
sso-type = "oauth"
strict-ssl = true
tag = "latest"
tag-version-prefix = "v"
timing = false
tmp = "/tmp"
umask = 2
unicode = true
unsafe-perm = true
update-notifier = true
usage = false
user = 1000
; user-agent = "npm/{npm-version} node/{node-version} {platform} {arch} {ci}" (overridden)
userconfig = "/home/ec2-user/.npmrc"
version = false
versions = false
viewer = "man"

Does this issue occur when all extensions are disabled?: Yes/No
Yes

[connor4312]

/duplicate #106537