fix: hide console window when running 'git rev-parse HEAD' on Windows

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!

[jwwisgerhof]

gitRevision() in packages/bundler-plugins/src/core/utils.ts runs execSync("git rev-parse HEAD", { stdio: [...] }) to auto-detect the release name. It passes no windowsHide, and Node's child_process defaults it to false. This is the fallback determineReleaseName() uses in local dev (when no CI/SENTRY_RELEASE env var is set).

When the bundler config is loaded by a console-less parent process, Windows allocates a new console for the git child and the default-terminal handoff renders it as a visible terminal window that flashes up and steals focus.

Real-world impact

This is probably quite limited in real world impact as this command should not be run on local dev machines. However, where it does, it fires constantly when running a Vite project inside (for example) an Nx workspace (nx serve): Nx's project-graph daemon reloads the Vite config — and thus the Sentry plugin's release detection — in a console-less plugin worker on every file save, so a terminal window flashes every single time you save a file. Surfaced via nrwl/nx-console#2906 (comment) (there's a companion fix in Vite for its own net use call).

Fix

Add windowsHide: true to the execSync options. No behavioural change to release detection; windowsHide does nothing on macOS/Linux.

Tests

Added a unit test asserting execSync is invoked with windowsHide: true.

[andreiborza]

Hi @jwwisgerhof, thanks for contributing this, sounds like a good improvement to me!