devExports: add bin to publishConfig

[Chewie]

Clear and concise description of the problem

Inside the exports configuration, the options devExports and bin do not play nice: while the exports do have a dual "src in exports"/"dist in publishConfig/exports", this is not the case for the bin, which only has the dist variant directly in the package.json "bin", and nothing in "publishConfig".

For example:

import { defineConfig } from "tsdown";

export default defineConfig({
  exports: {
    devExports: true,
    bin: {
      mybin: "./src/run.ts",
    },
  },
});

will produce in package.json:

"bin": {
  "mybin": "./dist/run.js"
}

According to https://pnpm.io/package_json#publishconfig, we can override "bin" in "publishConfig".

Suggested solution

It would be great if "bin" had the same behavior as exports, and would instead produce this:

"bin": {
  "mybin": "./src/run.ts"
},
"publishConfig": {
  "bin": {
    "mybin": "./dist/run.js"
  }
}

Cheers!

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sxzz]

In a typical local development workflow, the package bin usually does not end up in node_modules/.bin, so I’m trying to understand the use case for this. Could you share what scenario this feature is meant to support?

[Chewie]

Thanks for the response!

The scenario I'm in is a monorepo situation with two packages:

• one (let's call it "build-tool") produces a bin tool to do some codegen
• the other (let's call it "app") makes use of the tool for its own scripts, e.g. during its build.

So while it's not in the node_modules/.bin of build-tool, it is in the node_modules/.bin of app.

In the same way that dev exports point to src/ and not dist/, I'd like the ability to update the tool in its package, and run it in the other without having to run an explicit build.

The build-tool package will also be published standalone outside of the monorepo, hence the idea to make use of publishConfig so that real installs point to dist/, but local monorepo development for packages that depend on it point to src/

I've actually just made a reproduction repo for a different issue in another repo, but which is a mvp of what I'm doing in my monorepo: https://github.com/Chewie/turborepo-prune-docker-stub-bin-reproduction

Cheers,

[sxzz]

Thanks for your example! We will implement it