Skip to content
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

ENOENT: Bun could not find a file, and the code that produces this error is missing a better error. #10743

Open
samyarkd opened this issue May 1, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@samyarkd
Copy link

samyarkd commented May 1, 2024

What version of Bun is running?

1.1.6

What platform is your computer?

Ubuntu WSL

What steps can reproduce the bug?

remove bun lock file and try to add a new dependency, unless you run bun install the error still persists. but even after doing it still gives error after doing one installation. (it works only once per adding a new dependency).

What is the expected behavior?

a new lock file be created but it does not get created

What do you see instead?

no lock file

Additional information

No response

@samyarkd samyarkd added the bug Something isn't working label May 1, 2024
@raggesilver
Copy link

I've been getting this constantly while working on a monorepo with Bun workspaces. Running bunx shadcn-vue@latest add <any component> tries installing new dependencies, but fails (due to this issue). Running bun i and re-runing the shadcn-vue command works...

@rogersx27
Copy link

I got the same issue when a try bun i in Ubuntu WSL
image

But instead, I have the file bun.lockb
image

Any solutions?

@svenit
Copy link

svenit commented Jun 6, 2024

@rogersx27 let run npm i -g bun and run bun i again. It works for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants