For #269213
This adds a new eslint rule for `as any` and `<any>({... })`. We'd like to remove almost all of these, however right now the first goal is to prevent them in new code. That's why with this first PR I simply add `eslint-disable` comments for all breaks
Trying to get this change in soon after branching off for release to hopefully minimize disruption during debt week work
* refactor: Separate `createScriptRunnerTask` and `createInstallationTask` from `createTask`
* feat: Add `npm.scriptRunner`
* feat: Add Node.js as script runner
* refactor: Refactor `isPrePostScript`
* refactor: Extract `get*Command`
* fix: Typo
* style: Remove no-op `catch`es
* fix: `node --run` doesn't support `--silent`
* refactor: Use `.map` in `escapeCommandLine`
* chore: Remove TODO
Upstream reviewer is ok with current state
* fix: Fix error the resolved task definition differs from the original
* refactor: Separate `createScriptRunnerTask` and `createInstallationTask` from `createTask`
* feat: Add `npm.scriptRunner`
* feat: Add Node.js as script runner
* refactor: Refactor `isPrePostScript`
* refactor: Extract `get*Command`
* fix: Typo
* style: Remove no-op `catch`es
* fix: `node --run` doesn't support `--silent`
* refactor: Use `.map` in `escapeCommandLine`
* chore: Remove TODO
Upstream reviewer is ok with current state
This keeps our npm logic in one place and avoids activating the heavier-
weight `js-debug` extension on every .json file.
Also, use the same command to debug both from the explorer and
from script lens.
Fixes https://github.com/microsoft/vscode-js-debug/issues/782
Detects the preferred package manager
and if multiple are present, warns and uses
in priority order: npm => yarn => pnpm
Fixes#102050
Co-authored-by: Alex Ross <alros@microsoft.com>
Detects the preferred package manager
and if multiple are present, warns and uses
in priority order: npm => yarn => pnpm
Fixes#102050
Co-authored-by: Alex Ross <alros@microsoft.com>
