Skip to content

Commit 72640c3

Browse files
docs(node): document pre-bundled items and how to opt out
1 parent 69ea159 commit 72640c3

1 file changed

Lines changed: 24 additions & 0 deletions

File tree

src/node/NOTES.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,27 @@
1+
## Pre-bundled items
2+
3+
> [!NOTE]
4+
> Beyond the core install, this feature also sets up a few items by default for convenience — recommended VS Code extensions (such as a linter) and supporting tools. This is intentional behavior shared across features in this repository.
5+
6+
## Excluding pre-bundled items
7+
8+
Exclude a bundled **VS Code extension** by prefixing its ID with `-`, or disable a bundled **tool** by setting its option to `none` :
9+
10+
```json
11+
{
12+
"features": {
13+
"ghcr.io/devcontainers/features/node:2": {
14+
"pnpmVersion": "none"
15+
}
16+
},
17+
"customizations": {
18+
"vscode": {
19+
"extensions": [ "-dbaeumer.vscode-eslint" ]
20+
}
21+
}
22+
}
23+
```
24+
125
## Using nvm from postCreateCommand or another lifecycle command
226

327
Certain operations like `postCreateCommand` run non-interactive, non-login shells. Unfortunately, `nvm` is really particular that it needs to be "sourced" before it is used, which can only happen automatically with interactive and/or login shells. Fortunately, this is easy to work around:

0 commit comments

Comments
 (0)