peni4142
peni4142

Reputation: 555

My Visual Studio Code Extension does not show up in the sidebar

Have somebody an idea why my extension is not showing up in the sidebar ín Visual Studio Code? If I bring the extension in my extension folder, the extension works but do not show up in the sidebar.

Repo: https://github.com/peni4142/work-as-two

package.json:

{
    "name": "work-as-two",
    "displayName": "work-as-two",
    "author": {
        "name": "peni4142"
    },
    "description": "Opens the associated file for simultaneous work on two files.",
    "version": "0.1.0",
    "icon": "work-as-two.jpg",
    "license": "GPL-3.0-or-later",
    "keywords": [
        "tdd",
        "testdriven",
        "web",
        "html",
        "css"
    ],
    "repository": {
        "url": "https://github.com/peni4142/work-as-two"
    },
    "publishConfig": {
        "registry": "https://npm.pkg.github.com/"
    },
    "engines": {
        "vscode": "^1.41.0"
    },
    "categories": [
        "Other"
    ],
    "activationEvents": [
        "*"
    ],
    "main": "./dist/extension.js",
    "contributes": {},
    "scripts": {
        "vscode:prepublish": "npm run build",
        "compile": "webpack --mode development",
        "watch": "webpack --mode development -w",
        "pretestVscode": "npm run compile",
        "test": "mocha -r ts-node/register src/**/*.test.ts -u tdd",
        "testVscode": "node ./out/test/runTest.js",
        "build": "webpack --mode production"
    },
    "devDependencies": {
        "@types/glob": "^7.1.1",
        "@types/mocha": "^5.2.7",
        "@types/node": "^12.11.7",
        "@types/vscode": "^1.41.0",
        "glob": "^7.1.5",
        "ts-loader": "^6.2.1",
        "ts-node": "^8.6.2",
        "tslint": "^5.20.0",
        "typescript": "^3.6.4",
        "vscode-test": "^1.2.2",
        "webpack": "^4.41.5",
        "webpack-cli": "^3.3.10"
    }
}

Upvotes: 2

Views: 8762

Answers (1)

Gama11
Gama11

Reputation: 34158

It looks like VSCode no longer shows extensions with an undefined publisher in the extensions list (this definitely used to work at some point). If I add "publisher": "test" to "package.json" it shows up:

It occurred to me to try this because of the undefined_publisher in the Log (Extension Host) output channel:

[2020-02-03 20:43:03.326] [exthost] [info] ExtensionService#_doActivateExtension undefined_publisher.work-as-two {"startup":true,"extensionId":{"value":"undefined_publisher.work-as-two","_lower":"undefined_publisher.work-as-two"},"activationEvent":"*"}

Note that cloning extensions directly into the extensions directory is not an officially supported workflow, so things like this can break at any time.

Upvotes: 2

Related Questions