Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

Not available

Which canary version will you have in your reproduction?

2.5.5-canary.0

Environment information

CLI:
   Version: 2.5.5-canary.0
   Daemon status: Running
   Package manager: bun

Platform:
   Architecture: aarch64
   Operating system: macos
   WSL: false

Environment:
   CI: None
   Terminal (TERM): xterm-256color
   Shell (SHELL): /bin/zsh
   stdin: false

Expected behavior

I expect it to work without warning.

Actual behavior

I see this warning every time I run the turbo command, locally or CI.

WARNING Unable to calculate transitive closures: No lockfile entry found for '@emnapi/wasi-threads'.

To Reproduce

1. Create a project using the startup repository according to the documentation: bunx create-turbo@latest
2. After installing it, go to the project and run a command, e.g. bun run lint - notice there's no warning right now
3. Run cd web && bun add -d @tailwindcss/vite - this is the dependency that causes the problem
4. Run bun run lint (from root ofc) - now you should see the warning

$ turbo run lint
turbo 2.5.5-canary.0

 WARNING  Unable to calculate transitive closures: No lockfile entry found for '@emnapi/core'
• Packages in scope: @repo/eslint-config, @repo/typescript-config, @repo/ui, docs, web
• Running lint in 5 packages
• Remote caching disabled
┌─ @repo/ui#lint > cache hit (outputs already on disk), replaying logs 0bc77abf29e562fe 

$ eslint . --max-warnings 0
└─ @repo/ui#lint ──
┌─ docs#lint > cache hit (outputs already on disk), replaying logs f73866bbc3d334ad 

$ next lint --max-warnings 0
✔ No ESLint warnings or errors
└─ docs#lint ──
┌─ web#lint > cache hit (outputs already on disk), replaying logs 495857fedc54924f 

$ next lint --max-warnings 0
✔ No ESLint warnings or errors
└─ web#lint ──

 Tasks:    3 successful, 3 total
Cached:    3 cached, 3 total
  Time:    61ms >>> FULL TURBO

Additional context

As you can see It seems the problem is caused by @tailwindcss/vite. I've tested it with both the latest stable version (2.5.4) and the canary (2.5.5-canary.0), and the issue persists in both. I'm not sure whether the problem lies in @tailwindcss or in turbo.
I found only one similar issue reported here, but the thread is quite old and suggests that the problem should have already been resolved in a previous release. Thanks for taking the time to look into this.