prometheansacrifice

```json "path/to/exe-package": { "main": "MyBinary.re", "require": ["my-package/lib/here", "@reason-native/console"] } ``` `MyBinary` is the name of the main file ie `MyBinary.re` which creates `MyBinary.exe`. This way keys always have path to...

@jaredly How do we differentiate between exe and a lib? I like that the config would look simpler ```json "path/to/exe-package": { "require": ["my-package/lib/here", "@reason-native/console"] } "path/to/lib-package": { "require": ["my-package/lib/here", "@reason-native/console"]...

We can introduce the bin property like npm as we discussed.

> SomeEntrypoint.re as binary-name.exe :+1: > In this proposal the bin field is required every time you want to mark something a binary. Agreed.

> SomeEntrypoint.re as binary-name.exe While it can lead to confusion in a case insensitve file system, I do believe we should allow SomeEntrypoint.exe by default without having to specify the...

Missed #967 Going to review it when I can

@robz Would you like to take it over? I can see that a lot of interesting changes have landed on master and it could take a while for me to...

If not, I'll try in a few weeks

Couple of things 1. The postinstall.js isn't identical to the one esy creates on running the release command. On Windows, it was incorrectly trying set the env variable 2. The...

Marking my PR as a draft so that we can test this PR when the esy build is actually ready