❌ @dylan-conway, your commit has failing tests :(

💪 1 failing tests Darwin AARCH64

• test/js/web/fetch/fetch.test.ts 1 failing

🐧💪 1 failing tests Linux AARCH64

• test/integration/next-pages/test/next-build.test.ts 1 failing

🪟💻 4 failing tests Windows x64 baseline

• test/cli/install/registry/bun-install-registry.test.ts 1 failing
• test/cli/install/registry/bun-install-windowsshim.test.ts code 1
• test/js/bun/io/bun-write.test.js 1 failing
• test/js/node/child_process/child_process.test.ts 1 failing

🪟💻 3 failing tests Windows x64

• test/cli/install/registry/bun-install-registry.test.ts 5 failing
• test/cli/install/registry/bun-install-windowsshim.test.ts code 1
• test/js/node/child_process/child_process.test.ts 1 failing

View logs

windows test failures

Was curious to know if this might be making it into a release soon? The team over here at Motion is pretty anxious to try and swap yarn out for bun at the install layer and we think this is the last blocker.

Was curious to know if this might be making it into a release soon? The team over here at Motion is pretty anxious to try and swap yarn out for bun at the install layer and we think this is the last blocker.

Exactly the same situation over here. 😅

Was curious to know if this might be making it into a release soon? The team over here at Motion is pretty anxious to try and swap yarn out for bun at the install layer and we think this is the last blocker.

Same here

@Scalahansolo @flokol120 @Thiagolino8 We plan to have this included in the next release (1.1.18). There isn't a date for the release yet, but I would expect first half of next week