René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Conflict: dev-config installs nvm4w but TypeScript workload installs Node.js LTS directly","articleBody":"## Summary\n\nThe main `dev-config.winget` installs **NVM for Windows** (`CoreyButler.NVMforWindows`), which manages Node.js versions via a symlink at `C:\\nvm4w\\nodejs` and adds that to PATH. However, the **TypeScript workload** (`Workloads/typescript/configuration.winget`) separately installs `OpenJS.NodeJS.LTS` directly via winget, which places Node at `C:\\Program Files\\nodejs`.\n\nThis creates a broken state where:\n1. PATH points to `C:\\nvm4w\\nodejs` (set by nvm4w)\n2. The nvm4w symlink targets a version directory (e.g. `C:\\Users\\\u003cuser\u003e\\AppData\\Local\\nvm\\v24.16.0`) that **does not exist** because Node was installed via the MSI package, not through `nvm install`\n3. `node` and `npm` are not found on PATH despite Node.js being physically installed\n\n## Steps to Reproduce\n\n1. Apply the main `windows-dev-config/dev-config.winget` (installs nvm4w, adds `C:\\nvm4w\\nodejs` to PATH)\n2. Apply `Workloads/typescript/configuration.winget` (installs `OpenJS.NodeJS.LTS` to `C:\\Program Files\\nodejs`)\n3. Open a new terminal\n4. Run `node --version` → **command not found**\n\n## Root Cause\n\nnvm4w owns the PATH entry (`C:\\nvm4w\\nodejs`) and expects Node to be installed via `nvm install \u003cversion\u003e` + `nvm use \u003cversion\u003e`. The direct winget install of `OpenJS.NodeJS.LTS` puts node elsewhere and nvm4w's symlink points to a non-existent directory.\n\n## Suggested Fix\n\n**Option A** — TypeScript workload defers to nvm4w:\nReplace the `OpenJS.NodeJS.LTS` winget package resource with a `RunCommandOnSet` that runs:\n```powershell\nnvm install lts\nnvm use lts\n```\n\n**Option B** — Remove nvm4w from dev-config, let workloads install Node directly:\nRemove `CoreyButler.NVMforWindows` from `dev-config.winget` and ensure `C:\\Program Files\\nodejs` ends up on PATH (the Node MSI installer does this by default).\n\n**Option C** — Keep both but coordinate PATH:\nIf both are intentional, the TypeScript workload should add `C:\\Program Files\\nodejs` to PATH explicitly, or the `refresh-path.ps1` should detect and resolve the nvm4w symlink conflict.\n\n## Environment\n\n- Windows 11 (Build 2026)\n- winget v1.28.240\n- CoreyButler.NVMforWindows 1.2.2\n- OpenJS.NodeJS.22 24.16.0 (installed by winget as the LTS package)","author":{"url":"https://github.com/floatingsidewal","@type":"Person","name":"floatingsidewal"},"datePublished":"2026-06-03T15:58:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/55/WindowsDeveloperConfig/issues/55"}