-
Notifications
You must be signed in to change notification settings - Fork 616
Bump @biomejs/biome from 2.3.1 to 2.3.2 #656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔧 Build Fix:
Vitest worker process race condition causes EPIPE errors during test cleanup. The tests pass but the process exits with error code 1, causing the build to fail.
View Details
📝 Patch Details
diff --git a/apps/app/vitest.config.mts b/apps/app/vitest.config.mts
index 0866bcb..fabada1 100644
--- a/apps/app/vitest.config.mts
+++ b/apps/app/vitest.config.mts
@@ -6,6 +6,12 @@ export default defineConfig({
plugins: [react()],
test: {
environment: "jsdom",
+ pool: "threads",
+ poolOptions: {
+ threads: {
+ singleThread: true,
+ },
+ },
},
resolve: {
alias: {
Analysis
Vitest EPIPE error causing test failures
What fails: App tests pass but exit with EPIPE error during worker process cleanup, causing turbo run build to fail
How to reproduce:
cd apps/app && pnpm run testResult:
✓ __tests__/sign-in.test.tsx (1 test) 19ms
✓ __tests__/sign-up.test.tsx (1 test) 20ms
Test Files 2 passed (2)
Tests 2 passed (2)
Error: write EPIPE
at ChildProcess.target._send (node:internal/child_process:877:20)
at ForksPoolWorker.send (...vitest/dist/chunks/cli-api.D24RdiHp.js:6559:13)
38c41e8 to
f58b7cf
Compare
Bumps [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) from 2.3.1 to 2.3.2. - [Release notes](https://github.com/biomejs/biome/releases) - [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md) - [Commits](https://github.com/biomejs/biome/commits/@biomejs/[email protected]/packages/@biomejs/biome) --- updated-dependencies: - dependency-name: "@biomejs/biome" dependency-version: 2.3.2 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
f58b7cf to
c2222a7
Compare
Bumps @biomejs/biome from 2.3.1 to 2.3.2.
Release notes
Sourced from
@biomejs/biome's releases.... (truncated)
Changelog
Sourced from
@biomejs/biome's changelog.Commits
6d95a67ci: release (#7887)c600618feat(lint): implementnoIncrementDecrement(#7859)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)