vercel / vercel/next-devtools-mcp
Won't calling `process.exit(0)` in browser-eval-manager cause a bug?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 822
- Forks
- 67
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
src/_internal/browser-eval-manager.ts
// browser-eval-manager.ts
process.on("SIGINT", async () => {
await stopBrowserEvalMCP()
process.exit(0) <--- this part
})
process.on("SIGTERM", async () => {
await stopBrowserEvalMCP()
process.exit(0) <--- this part
})
Won't telemetry data be lost if I exit immediately?
Contributor guide
No contributing guide indexed for this repository
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
Read src/_internal/browser-eval-manager.ts, focusing on the SIGINT and SIGTERM handlers and their call to stopBrowserEvalMCP(). Trace how telemetry is shut down before process.exit(0). Done means determining whether immediate exit can lose telemetry and documenting or addressing the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100