Skip to content

Bound background native TypeScript project checks - #18

Draft
QuentinCody wants to merge 1 commit into
review/public-cli-20261119from
fix/native-compiler-cpu-20261119
Draft

QuentinCody wants to merge 1 commit into
review/public-cli-20261119from
fix/native-compiler-cpu-20261119

Conversation

@QuentinCody

Copy link
Copy Markdown
Owner

The harness daemon now gives background native TypeScript project checks a default of two Go scheduler threads. It applies that default to both synchronous and asynchronous project checks, including after a cold start. An explicit GOMAXPROCS in the launch environment takes precedence.

Foreground verification, the JavaScript TypeScript compiler and standalone file checks keep their existing execution settings.

Verified with focused compiler-runner tests, typechecking and an ordinary Node 22 build. This change is stacked on #17.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant