Export bins from package

[nojaf]

This is convenient to have.

[pkg-pr-new]

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript-lang/rescript@7530

@rescript/darwin-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@7530

@rescript/linux-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@7530

@rescript/linux-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@7530

@rescript/win32-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@7530

@rescript/darwin-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@7530

commit: 0b047ad

[cometkim]

What's this?

[cometkim]

I intentionally did not export this because I do not want to make it a public API yet. If we exported this, it would be the first compiler API surface. Then we need to discuss its shape more carefully.

[nojaf]

That is why I marked the changelog entry as internal.

I've used the trick mentioned here a few times, and it would be more convenient to have this without the dynamic import.

I believe we don't need to finalize the entire compiler API to export some binary paths. This is an internal, undocumented API with no guarantees.

[cknitt]

I am also a bit hesitant about exporting this. I am afraid that as soon as it's there, people will start abusing it.

Even though undocumented, it's not really clear from the name "binaries" that this is internal API.