Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Bun binary creates a dot folder in the home dir by default #965

Closed
lgarron opened this issue Aug 2, 2022 · 3 comments
Closed

Bun binary creates a dot folder in the home dir by default #965

lgarron opened this issue Aug 2, 2022 · 3 comments
Labels
bug Something isn't working needs repro Needs an example to reproduce

Comments

@lgarron
Copy link
Contributor

lgarron commented Aug 2, 2022

Version

Current install

Platform

macOS

What steps will reproduce the bug?

The install command on the website: curl https://bun.sh/install | bash

How often does it reproduce? Is there a required condition?

Consistently.

What is the expected behavior?

I don't end up with a new dot folder in my home dir.

What do you see instead?

bun was installed successfully to ~/.bun/bin/bun 

Added "~/.bun/bin" to $PATH in "~/.config/fish/config.fish" 

Additional information

When I try out a new program and it insists on creating a new dot file or dot directory in my home folder, it's an immediate red flag for me. 😕 In this case, I wanted to try out bun, but uninstalled it immediately. I understand that I can move the folder, but I'd be concerned that this would break e.g. auto-updates in the future. I thought I'd file an issue rather than ignoring it.

I'd appreciate if bun used a an alternative like:

@lgarron lgarron added bug Something isn't working needs repro Needs an example to reproduce labels Aug 2, 2022
@Jarred-Sumner
Copy link
Collaborator

Bun creates a dot folder for caching with bun install and for global bins with bun install

@lgarron
Copy link
Contributor Author

lgarron commented Aug 3, 2022

Bun creates a dot folder for caching with bun install and for global bins with bun install

Apologies, maybe I should have been more clear — I'm asking for for bun not to do this, and to use other conventions instead. Shall I take your response as a wontfix / should I file more specific requests? Thanks!

EDIT: looks like #696 covers the cache dir case. The question still remains for ~/.bun/bin as created by the bun installer script.

@s373r
Copy link

s373r commented Jun 3, 2024

For future readers -- to install to a different directory that is convenient for you (e.g., ~/.local/share/bun), you can use the following command:

curl -fsSL https://bun.sh/install | BUN_INSTALL="${HOME}/.local/share/bun" bash

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working needs repro Needs an example to reproduce
Projects
None yet
Development

No branches or pull requests

3 participants