docs(node): document pre-bundled items and how to opt out#1695
Open
V-Subhankar-infy wants to merge 2 commits into
Open
docs(node): document pre-bundled items and how to opt out#1695V-Subhankar-infy wants to merge 2 commits into
V-Subhankar-infy wants to merge 2 commits into
Conversation
Added notes on excluding pre-bundled items and VS Code extensions.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds Node feature documentation clarifying what gets pre-bundled by default and how consumers can opt out of those defaults.
Changes:
- Documented that the feature includes pre-bundled convenience items (VS Code extensions and supporting tools).
- Added an example showing how to exclude a bundled VS Code extension and disable a bundled tool via
none.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Corrected formatting and punctuation in the NOTES.md file.
Comment on lines
+36
to
+37
| Exclude a bundled **VS Code extension** by prefixing its ID with `-`, or disable a bundled **tool** by setting its option to `none`: | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs(node): document pre-bundled items and how to opt out
Aimed to Solve #1693 · Related: #386
Problem
The
nodefeature installs recommended extensions (e.g.dbaeumer.vscode-eslint)and tools (yarn, pnpm) by default, but this isn't documented. Users wanting only
Node.js are surprised and find no opt-out guidance — the same concern raised in
#386 for the Node and Go features.
Options considered
inconsistent with sibling features.
never implemented as it needs a spec change; the native VS Code
-<id>syntaxnow fills this role.
-<id>opt-out: chosen.Why this option
The behavior is intentional and the
-<id>opt-out already exists — only thedocumentation was missing. It's non-breaking, zero-risk, and directly answers
what users asked in #1693 and #386.
Changes
Adds a short "Pre-bundled items" note to
src/node/NOTES.mddescribing the defaultextensions/tools and how to exclude them (extension →
-<id>, tool → option"none"). The README is auto-generated, so it regenerates on merge.Impact
Docs-only — no behavioral change and no runtime risk. Users get clear, discoverable
opt-out guidance, which should reduce duplicate reports.
Future action
Only node is covered here; ~14 other features bundle extensions too. The durable fix
is to auto-emit this note from the docs generator (
devcontainers/action, tracked inaction#139) rather than copying it per-feature.