Michael H

> which tests? looks like they're all passing in CICD afaict I'm not sure why its green status, but if you press "details" it will send you to the page:...

Yeah I think it was `bun run` closing instead of passing in the SIGINT message to the process. I believe `bun ./index.ts` or `bunx vite` should still work though. (also...

Interesting, it appears to treat each line as a very separate instance. Like if you use `&&` instead, then it will exit. This is further shown when you run an...

The issue seems to be because of the `tsconfig.json` and its `baseUrl`. It means bun checks it first on what to resolve (as there is `react.ts`, bun thinks that is...

> can you verify if this still occurs with `11.14.4`? As I believe the tsconfig.json is correctly excluded from the npm bundle now. > https://github.com/motiondivision/motion/issues/2918 @codehz I believe the upstream...

> seems to work on macos, so id probably save this for later considering your current priority isnt to support aarch64 termux I can confirm that on github actions, it...

For anyone wondering a temporary solution: ```py # install fixed version from pr $ bunx bun-pr 14501 # run your scripts with it $ bun-14501 run index.ts ``` The issue...

This sounds like the Vite/Svelte Kit bundler doesn't understand the `bun` import and is as a result removing it. There was a similar issue on next.js that was recently fixed...

Can confirm this behavior. Also worth noting `bun build ... | bun -` doesn't work either. The bug seems to be that bun is replacing the `module` into `require.module` which...

It looks like `node:test` does pretend to be `bun:test` now: https://github.com/oven-sh/bun/blob/main/src/js/node/test.ts However I don't think its fully supported nicely as it uses `assert from 'node:assert'` instead of `expect` api