Two submissions from the same reader report that the npm (non-Docker) install on Windows breaks, and that /docs/local/npm has no troubleshooting section to work from.
Reports (verbatim, sanitized)
"windows build sometimes started failing. 14 aug 2026 - ok, later updates i just get errors. Could be symlink issues or something, hard to tell, but windows path maybe treated wrong. So maybe topic covering common errors could be great"
"and yes, it me again about windows and topics to fix issues, hit me up if need"
The reporter left a contact handle and offered to help reproduce.
Current state
content/docs/local/npm.mdx documents the happy path only. It has no troubleshooting section and no Windows-specific notes.
Why this is filed rather than fixed
The automation could not reproduce the failure: it has no Windows environment, and the report does not name a specific error. Writing Windows failure causes without a reproduction would mean inventing them. What is needed is one person to run the npm install path on Windows, capture the actual errors, and write them up.
Discord feedback IDs: 1514808463547437227, 1514808601586307083.
Two submissions from the same reader report that the npm (non-Docker) install on Windows breaks, and that
/docs/local/npmhas no troubleshooting section to work from.Reports (verbatim, sanitized)
The reporter left a contact handle and offered to help reproduce.
Current state
content/docs/local/npm.mdxdocuments the happy path only. It has no troubleshooting section and no Windows-specific notes.Why this is filed rather than fixed
The automation could not reproduce the failure: it has no Windows environment, and the report does not name a specific error. Writing Windows failure causes without a reproduction would mean inventing them. What is needed is one person to run the npm install path on Windows, capture the actual errors, and write them up.
Discord feedback IDs: 1514808463547437227, 1514808601586307083.