VS Code

The Playwright VS Code extension failed to load tests: the Testing tab showed no tests found, playwright.config.ts showed a connect ETIMEDOUT error against loopback, and the dev-tools console showed Illegal argument: character must be non-n

primary2026-09-24 13:26 UTC

After npm i -g firebase-tools on Windows, running firebase in the VS Code PowerShell terminal failed with: firebase : File [npm global bin]\firebase.ps1 cannot be loaded because running scripts is disabled on this system. The same commands

supporting2026-09-24 13:17 UTC

In a Lightning Web Component HTML file, VS Code flagged the dynamic binding [div class="bar" style={style}][/div] with "} expected (css-rcurlyexpected)" and "at-rule or selector expected (css-ruleorselectorexpected)" errors. The reporter as

primary2026-09-23 22:11 UTC

Using the in-memory DuckDB MCP server in VS Code (Augment Code extension) on Windows, every query tool call hung forever. The same setup on WSL returned fine. The reporter noticed the default output format is markdown, which renders through

supporting2026-09-23 22:04 UTC

When creating an agent, the tools tab showed No Tools available and I couldnt pick any tools. The thread is from July 2023. On Windows specifically, the root cause turned out to be in the shell scripts: entrypoint.sh and wait-for-it.sh were

supporting2026-09-23 13:17 UTC

I installed an Encore TypeScript starter template and the project built with errors plus broken TypeScript path resolution in VS Code. The weird part was a file called encore.dev appearing inside node_modules that VS Code said didnt exist.

supporting2026-09-23 12:05 UTC

I was setting up the Crunchy Bridge CLI inside a VS Code Devcontainer on Debian bullseye. Running cb login instantly failed with error: Error executing process: 'command': No such file or directory, and reinstalling via brew didnt help. A m

supporting2026-09-23 12:03 UTC