How to mark an entry point as executable (shebang)

[snebjorn]

I've got this executable in entry config

export default defineConfig({
  entry: ['src/bin/orval.ts'],
});

But when I tried out Package Exports a bin entry wasn't added to the publishConfig

So I was wondering. Is this a bug or have I misconfigured something?

[sxzz]

Did you mean bin field? bin is not included in exports feature.

[snebjorn]

is there a reason bin is not included? Should I not use the exports feature with the bin field?

[sxzz]

The bin field can be an object, and its property names must be defined by the user.

"bin": {
  "cli-name-a": "./dist/a.mjs",
  "cli-name-b": "./dist/b.mjs"
}

[snebjorn]

if I have

"bin": {
  "cli-name-a": "./src/a.ts"
},
"publishConfig": {
  "bin": {
    "cli-name-a": "./dist/a.mjs"
  }
}

The package exports feature changes it to

"bin": "./src/a.ts",
"publishConfig": {
  "bin": {
    "cli-name-a": "./dist/a.mjs"
  }
}

It doesn't touch publishConfig, but it changes bin

[snebjorn]

hmm, seems I'm wrong about this. It does do it now. But I'm sure it changed it at some point.

[snebjorn]

okay... it does change bin

[snebjorn]

The package exports feature adds the entry executable to exports along with bin. I'm not sure adding the executable to exports is intended.
When I look at the d.ts file it just has export { }; which is expected. So having it in exports is just noise :)