Would be neat to also support bun publish -r for monorepos, similar to pnpm.

Some workaround?

Since I would like to use only bun without installing node at all. I would also like to have a way to publish my packages

I'm converting some of the tinyhttp stuff to use with Bun and it's the only thing preventing it right now

Here is a simple implement without publish hooks (just work)

https://github.com/innoai-tech/nodekit/tree/main/nodedevpkg/bunpublish (published https://github.com/orgs/innoai-tech/packages/npm/package/bunpublish)

reuse install.registry.token, but may publish.registry.token in future

split as single package https://github.com/morlay/bunpublish

If/ when this gets implemented, it would be awesome if publishConfig respected main like Yarn does.

My use case is changing the main property from ./src/index.ts during development to ./out/index.js at publish time. This way I can use internal packages in development, but also publish them as external packages.

@vveisard may consider to use export condition instead.

"exports": {
    "bun": "./src/index.ts",
    "import": "./out/index.js"
}

Realword example: https://github.com/innoai-tech/nodekit/blob/main/nodepkg/config/package.json#L21-L43
which support nodejs too.

Any update for this?

Any update for this?

Here's where discussions and updates relevant to that issue are posted: #1976

Running into this because the simple workaround to use npm for publishing does not easily work with bun workspaces.
If the publish command is not implemented, it would be nice to be able to reference packages in a workspace without the workspace: prefix, such that npm can process it.

Since I would like to use only bun without installing node at all. I would also like to have a way to publish my packages

You can run bun install -g npm to get npm without node, but npm (should) need node. You can run bunx --bun npm to run npm with bun. Both work on my machine, though I have both node and bun so it's hard to tell if they're working as intended.

Using bunx --bun npm is a great idea to run npm without Node.js. That should enable publishing npm packages entirely with Bun, solving these related issues.

• Implement bun publish #1976
• Creating an NPM package using Bun #6034

When I first ran bunx --bun npm, it was running an existing installation of npm from Node.js. Specifying npm@latest downloaded it to /tmp and ran with Bun for sure.

So it should be possible to publish to npm registry with the following command. The --bun option seems to be unnecessary. I tried with --dry-run option and it looks like it works.

bunx npm@latest publish

@dylan-conway is working on it this week

Hope that I can replace workspace:* when it's published.

Great to hear that an implementation is underway. Would be great if the publish command could be made to work off of CLI arguments & env vars without needing any config files like .npmrc (which is currently necessary when using auth tokens).

Currently, when using a bun-only workflow, an .npmrc is still needed just for the auth token. Would be great to rely on the CLI alone.

bun publish will ship as part of the Bun v1.1.30 release, thanks to @dylan-conway