vscode.provideDocumentSemanticTokens returns null when using native preview with built-in TS extension disabled

[jw0785]

🔎 Search Terms

vscode.provideDocumentSemanticTokens

🕗 Version & Regression Information

• textDocument/semanticTokens/full are computed as shown in output panel.
• editor renders semantic highlighting correctly
• But vscode.provideDocumentSemanticTokens returns null/undefined when called from another extension
• other language ext that register DocumentSemanticTokensProvider works though. even pwsh

⏯ Playground Link

No response

💻 Code

// Your code here

🙁 Actual behavior

inconsistent sem token return

🙂 Expected behavior

should be consistent in output panel and when called from another ext

Additional information about the issue

No response

[InfinityFreakUniverseBoy]

🔎 Search Terms

vscode.provideDocumentSemanticTokens

🕗 Version & Regression Information

• textDocument/semanticTokens/full are computed as shown in output panel.
• editor renders semantic highlighting correctly
• But vscode.provideDocumentSemanticTokens returns null/undefined when called from another extension
• other language ext that register DocumentSemanticTokensProvider works though. even pwsh

⏯ Playground Link

No response

💻 Code

// Your code here

🙁 Actual behavior

inconsistent sem token return

🙂 Expected behavior

should be consistent in output panel and when called from another ext

Additional information about the issue

No response

[RyanCavanaugh]

We need a way to repro this so that we can be sure we're looking at the same codepath as you're hitting