microsoft / microsoft/vscode-generator-code

"No matching version found for @types/vscode@^1.113.0."

Open
#571 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.6k
Forks
262
Avg merge
15d 22h
Merged PRs (30d)
1

Description

When I try to create an extension with yo code, it fails to npm install at the end:

✔ What type of extension do you want to create? New Extension (TypeScript)
✔ What's the name of your extension? shutdown_repro
✔ What's the identifier of your extension? shutdown-repro
✔ What's the description of your extension?
✔ Initialize a git repository? No
✔ Which bundler to use? unbundled
✔ Which package manager to use? npm

Writing in D:\Dev\Temp Projects\shutdown-repro...
   create shutdown-repro\.vscode\extensions.json
   create shutdown-repro\.vscode\launch.json
   create shutdown-repro\.vscode\settings.json
   create shutdown-repro\.vscode\tasks.json
   create shutdown-repro\package.json
   create shutdown-repro\tsconfig.json
   create shutdown-repro\.vscodeignore
   create shutdown-repro\vsc-extension-quickstart.md
   create shutdown-repro\README.md
   create shutdown-repro\CHANGELOG.md
   create shutdown-repro\src\extension.ts
   create shutdown-repro\src\test\extension.test.ts
   create shutdown-repro\.vscode-test.mjs
   create shutdown-repro\.eslintrc.json

Changes to package.json were detected.

Running npm install for you to install the required dependencies.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @types/vscode@^1.113.0.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: C:\Users\danny\AppData\Local\npm-cache\_logs\2026-03-30T15_16_23_647Z-debug-0.log
Error code

Command failed with exit code 1: npm install

The last version of this package on npm seems to be 1.110.0 but it seems to be trying to get 1.113.0.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the generated package.json and the template that supplies its @types/vscode dependency, then reproduce the failure with npm install. Trace why the generated project requests an unavailable version, and verify that a newly generated TypeScript extension installs successfully with npm.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
cli, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
56/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.