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

Publish as package #6

Closed
gtrabanco opened this issue May 3, 2023 · 7 comments
Closed

Publish as package #6

gtrabanco opened this issue May 3, 2023 · 7 comments

Comments

@gtrabanco
Copy link

Can this be available through bun install by publishing in npmjs?

Installation would be easier by using bun add bkg.

@paulocoghi
Copy link

Despite being made in Bun, I see bkg more of an external tool/cli than a javascript library.

Yes, it is possible to install packages from npmjs globally as well, to use them as a tool/cli, but inattentive developers could end up mistakenly installing bkg internally in their projects (which also is simple to solve, by letting it clear on the docs).

Anyway, the suggestion isn't bad, but I'm concerned that this could create more work to the maintainers (I'm not one), because they would need to additionally publish the releases to npmjs and, on the other side, the project already provides a simple one command line to install it today.

Just my 2c.

@gtrabanco
Copy link
Author

Yes, I see the point. You are right.

Have more sense have formulas for brew, apt... I will probably do brew formula its easy and I have done some for myself. I will let you know when I have it, not sure when.

In order to not make the repository of issues about similar stuff... I see the runtime creation use only latest version of bun. I do not know zig but probably a option to compile to latest canary bun would be nice and automate runtime creation on a repository and let developer choose unstable branch. Whats your opinion about? Whatever it is your opinion I see like an independent repository for runtimes could be (probably) a good idea.

@gtrabanco gtrabanco reopened this May 3, 2023
@gtrabanco
Copy link
Author

I clicked close accidentally 😅 Sorry

@paulocoghi
Copy link

paulocoghi commented May 3, 2023

Sure, no problem! About your last input, I like it a lot but it would be better if Sayan himself could answer as well, since I'm not a maintainer/contributor.

@theseyan
Copy link
Owner

theseyan commented May 4, 2023

I do plan to eventually publish bkg as an npm package (it won't be bkg however as the name is already taken).

To answer @gtrabanco, being able to choose Bun versions (including canary) is already on the roadmap & will definitely arrive in a newer version. There will also likely be a separate repository for Bun binaries as the next version of bkg will have an option to generate smaller binaries.

@gtrabanco
Copy link
Author

Sorry I was going to make the homebrew package when I though about this issue... @theseyan you said you will rename bkg... Do you have any planned name? if you want that formulae to be on the brew core packages you should check if the name is taken in both sides before setting the final name. bkg is free on Homebrew. I think this could be accepted as core formulae.

@gtrabanco gtrabanco reopened this May 8, 2023
@gtrabanco
Copy link
Author

Forget it, it won't be accepted as core formulae. See this PR: Homebrew/homebrew-core#105263

One requirements its to compile from source and resolve all dependencies which won't be done by the moment with brew.

So it's mandatory to support our own tap. Maybe we can request to be in bun tap repository when the formulae it's done: https://github.com/oven-sh/homebrew-bun

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants