853bfec43a
The salvaged paragraph described one mechanism that is actually two. Per developer.chrome.com/blog/remote-debugging-port, Chrome 136+ simply stops respecting --remote-debugging-port/--remote-debugging-pipe against the default data dir — no dialog, nothing listens. The "Allow remote debugging?" prompt the contributor saw is the separate Chrome 144+ opt-in approval flow (chrome://inspect/#remote-debugging), which asks per incoming connection, not per launch. Say so, cite both sources, and keep the fix (non-default --user-data-dir, or use_real_profile) unchanged.
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.