I think that this is related to sideloading the extension. The file authority and schema are not what vscode are expected, so it doesn't know where to find the extension info. This causes VS Code to default to it's nullExtensionDescription.
When testing the same scenario on Desktop, it works fine:
I've confirmed that other extensions appear normal on vscode.dev, so I'm pretty sure this will be resolved once we actually publish the extension to the marketplace.
I think that this is related to sideloading the extension. The file authority and schema are not what vscode are expected, so it doesn't know where to find the extension info. This causes VS Code to default to it's
nullExtensionDescription.When testing the same scenario on Desktop, it works fine:
I've confirmed that other extensions appear normal on vscode.dev, so I'm pretty sure this will be resolved once we actually publish the extension to the marketplace.
The code for that logic is here: https://github.com/microsoft/vscode/blob/59608d3aee99b2599347b45efbc5f5ee23df56cd/src/vs/workbench/api/common/extHostRequireInterceptor.ts#L164-L184