ChromeDevTools / ChromeDevTools/chrome-devtools-mcp
Support console message templates
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 52.3k
- Forks
- 4.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 83
Description
Is your feature request related to a problem? Please describe.
Currently if a console log is a template, e.g., msgid=4 [log] %c %c %c %c %c Phaser v3.90.0 (WebGL | Web Audio) %c https://phaser.io/v390 background: #ff0000 background: #ffff00 background: #00ff00 background: #00ffff color: #ffffff; background: #000000 background: transparent (7 args) the template is shown as is.
Describe the solution you'd like
We should re-use Chrome DevTools frontend logic to resolve the template.
Describe alternatives you've considered
N/A
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the console-message handling entry point and the Chrome DevTools frontend logic mentioned in the request. Done means console messages using templates resolve their placeholders and formatting instead of being displayed as the raw template, with the behavior verified against the provided example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- devtools, typescript
- Domain
- devtools, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100