mix assets.deploy fails in Alpine Docker Env about esbuild HOT 5 CLOSED

The reason was that COPY also copied the local _build folder which contained the esbuild executable which was of the type esbuild: Mach-O 64-bit executable arm64 and therefor didn't run in our linux docker image. Would've still been great to have a more descriptive error ;)

from esbuild.

It's difficult to get a descriptive error for this case.
If the wrong esbuild binary thought for a different OS architecture is present,
the call to esbuild will possibly just fail (or even work and then fail).

But I understand if one stumble across this problem it's difficult to find the cause.

The current esbuild implementation does not have any information for which OS architecture the present esbuild binary is for.

The only solution I could think of, we would need to save the esbuild binary with the OS architecture information attached.
→ _build/esbuild-linux-64

Then at runtime always check the target and call the binary with it.

@josevalim May I ask you for your opinion? Is it worth it to go this way?

from esbuild.

@cw789 I think saving it as esbuild-linux64 doesn't hurt and we already have the logic to compute the architecture anyway. Can you please send a PR? :)

from esbuild.

Oh I'm glad filing this was still useful :)

from esbuild.

Can you please send a PR? :)

Sure, I love to do so.

Oh I'm glad filing this was still useful :)

Of course it is. Thanks.
Give me some time and we both won't stumble again over this problem.

from esbuild.