Glob syntax not supported for Windows out of the box [with esbuild]

[JenteSL]

Currently, the build script involves: esbuild app/javascript/*.* --bundle --outdir=app/assets/builds

On Windows, this results in an error: Could not resolve "'app/javascript/*.*'" (glob syntax must be expanded first before passing the paths to esbuild).

From what I've found troubleshooting, it appears that the glob syntax is a shell-specific feature. esbuild does not interpret it on its own. With PowerShell or CMD on Windows not supporting the glob syntax properly, the build commands doesn't work out of the box in these shell environments.

I'm not sure how to go on from here for a general solution. For now, in my project I changed the build script to reference the only .js file I have: esbuild app/javascript/application.js --bundle --outdir=app/assets/builds

[dhh]

Would be nice to have a section in the README about Windows considerations 👍

[dhh]

We could actually also detect Windows in the install script and change the default build script proposed. Feel free to have a look at that if you'd like!

[JenteSL]

Yeah, the only problem is that I'm not sure which command could do the trick on Windows, without specifying all the js files.

I'm not sure it is possible without an esbuild config file and something like an external glob package...

[dhh]

Documented it via 95e6b15