Allow libraries to recommend extensions

[justinfagnani]

I maintain a library, lit-html, where the developer experience within VS Code is greatly improved by an extension that provides syntax highlighting, linting, intellisense, etc. Unfortunately many people aren't aware of the extension, and don't get those benefits.

It would be great for our users if we could include some configuration in the package so that when a user imports our library they get a recommendation similar to what you see if you edit a file type that you don't have an extension for.

[justinfagnani]

@usernamehw I don't see how that helps.

I don't want my library to depend on the extension, since not every user of the library uses VS Code, and not every install of the library will be for users who are directly using it. We don't want to incur that download cost.

Then, there's only one extension in play here. There isn't another extension to depend on.

What I'm looking for is a way to add something like:

{
  "recommendations": ["runem.lit-plugin"]
}

(similar to workspace recommended extensions)

to my library's package.json, and have that extension be recommended to users who import modules from that package, and thus would benefit from the extension.

[usernamehw]

I deleted the comment after reading the issue the second time.

[vscode-triage-bot]

We closed this issue because we don't plan to address it in the foreseeable future. You can find more detailed information about our decision-making process here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!