Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Extension not being activated

Open
#413 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
devtools

Research direction

Start with the default TypeScript extension generated by the project and inspect its activation in the VS Code debug console. Reproduce the problem on the reported Arch Linux setup; done means the extension loads and reports activation in the debug console.

Written by the indexing model from the issue text.

Description

Hello, I am making an extension, if I run it, the extension doesn't even get loaded. It doesn't say that the extension is even activated, in the debug console. I have the default code generated by making a new typescript extension, I am using Arch Linux which was updated a few days ago.

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

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

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.

More from microsoft/vscode-generator-code

All issues in microsoft/vscode-generator-code

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.