Esy: Automatically configure "install" commands for package with *.install file present

[andreypopp]

If a package has a single *.install file in the source tree and don't have "esy.install" configuration in package.json then we could configure "esy.install" to be esy-installer invocation.

We would need to have esy-installer as a dependency of esy in that case (also inject it into an ejected buid) — this is the hard part.

This should be done in esy-build-package.

[jordwalke]

Also, do you think esy-installer should just come out of the box, without it ever having to be configured as a dependency? (Only challenge is if we need to version it)

[jordwalke]

@kennetpostigo had the same feedback about the install field when trying esy out the first time.
Nearly every package I've made so far has this default, and is hardly ever customized.

[rauanmayemir]

I started looking into this.

[jordwalke]

Whoever wants to tackle this one (you or @ELLIOTTCABLE) please let me know and I'll mark you assigned. This other task is related too, both of them fairly easy I think.