Summary
As a developer working closely with VS Code architecture and custom extension tooling, I would like to propose an enhancement to the core initialization and bootstrap processes (src/main.js / CLI bootstrap flow).
Specifically, providing cleaner extension hooks or enhanced diagnostic logging during the ESM bootstrap and NLS configuration phase (resolveNLSConfiguration) would greatly help developers debug startup behaviors and integrate custom CLI workflows.
Details / Use Case
Current Behavior: The core bootstrap cleanly initializes portable support, NLS configurations, and hands over to the CLI server (cli.js), but offers limited flexibility for external monitoring or safe injection of custom diagnostic layers during startup.
Proposed Feature: Introduce cleaner extension points or structured telemetry/logging hooks right after await bootstrapESM(); to allow developers to track startup performance and CLI launch flags (VSCODE_CLI) more transparently.
Does this issue relate to any existing documentation?
No
Summary
As a developer working closely with VS Code architecture and custom extension tooling, I would like to propose an enhancement to the core initialization and bootstrap processes (src/main.js / CLI bootstrap flow).
Specifically, providing cleaner extension hooks or enhanced diagnostic logging during the ESM bootstrap and NLS configuration phase (resolveNLSConfiguration) would greatly help developers debug startup behaviors and integrate custom CLI workflows.
Details / Use Case
Current Behavior: The core bootstrap cleanly initializes portable support, NLS configurations, and hands over to the CLI server (cli.js), but offers limited flexibility for external monitoring or safe injection of custom diagnostic layers during startup.
Proposed Feature: Introduce cleaner extension points or structured telemetry/logging hooks right after await bootstrapESM(); to allow developers to track startup performance and CLI launch flags (VSCODE_CLI) more transparently.
Does this issue relate to any existing documentation?
No