node feature and eslint extension

[skwde]

It is not clear to me why ghcr.io/devcontainers/features/node also installs the dbaeumer.vscode-eslint extensions.
As a user, who only wants node, this seems incorrect. It installs more than the feature actually says.

As per https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_85.md#opt-out-of-extensions I can opt-out, by adding "-dbaeumer.vscode-eslint".

Also https://github.com/devcontainers/features/blob/main/src/node/README.md gives no hint.

Related #386

[V-Subhankar-infy]

Hi @skwde,

Thanks for raising this, and for linking the earlier discussion.

The dbaeumer.vscode-eslint extension is bundled as an opinionated convenience default. Like most language features in this repo (e.g. go ships golang.Go, python ships ms-python.python), the node feature adds a recommended editor extension for a typical Node.js/JavaScript workflow. It has been part of the feature since very early on. Note that it only adds the VS Code extension , it does not install the eslint CLI itself.

I went through the conversation in #386, and it's clear that several users weren't aware they could opt out of bundled extensions in order to plug in their own preferred ones & ended up digging through issues to find a workaround.Since changing the default would disrupt the large number of existing users who rely on these bundled defaults, rather than alter the behavior, I'm opening a PR to address one of the issues here: the missing documentation. So that the Readme itself clearly states that the feature ships with a small recommended extension bundle and explains how to opt out.

Please take a look at the changes in the PR #1695 and do let me know if this solves your problem for now.