Hey there! We use (and love) Laravel Mix in the Lucky framework for Crystal. We actually check for a manifest.json file at compile-time to help guarantee that assets you're requesting exist, which is really neat!
To that end, we have a script/setup Bash script that initializes your app and generates the manifest.json. Recently, running only mix seems to have started blocking the terminal for input, meaning that we could no longer use it in a Bash script or CI context.
We're thinking that the solution will be to simply run yarn prod (a wrapper script for mix --production), but it does seem a bit weird to run a production compilation in a development/CI environment just to get the manifest file.
Is there a way to run mix without blocking on input, or to generate only the manifest file?
mix in a non-interactive environment (like GitHub actions)mix command causes the workflow to hangHere is the workflow on our website where we noticed the issue
Mix does not wait for input. You are using the in-preview Tailwind JIT engine which, by default, starts a watcher when NODE_ENV=development. To fix this set the TAILWIND_MODE=build env var.
馃う Thanks, @thecrypticace!
Happy to help!
Most helpful comment
馃う Thanks, @thecrypticace!