c7e187f893
Fixes #16442 The current instructions on the Debugging page currently only work for server-side code, and furthermore, the page doesn't actually _say_ that they only work for server-side code. This update adds instructions for debugging client-side code in both VS Code and Chrome DevTools. It also improves the suggested VS Code launch configurations to take advantages of some relatively recent features in VS Code's [built-in JavaScript debugger][1]. Using the `node-terminal` and `pwa-chrome` launch types removes the need to manually pass an `--inspect` flag to the underlying Node.js process. [1]: https://github.com/microsoft/vscode-js-debug Let me know if there are any edge cases I didn't consider with these VS Code launch configs! ## Documentation / Examples - [x] Make sure the linting passes |
||
---|---|---|
.. | ||
amp-support | ||
automatic-static-optimization.md | ||
codemods.md | ||
custom-app.md | ||
custom-document.md | ||
custom-error-page.md | ||
custom-server.md | ||
customizing-babel-config.md | ||
customizing-postcss-config.md | ||
debugging.md | ||
dynamic-import.md | ||
i18n-routing.md | ||
measuring-performance.md | ||
module-path-aliases.md | ||
multi-zones.md | ||
preview-mode.md | ||
security-headers.md | ||
source-maps.md | ||
src-directory.md | ||
static-html-export.md |