Live Reload Loop Issue with Quinoa in a Monorepo Project

[haikalrios]

We are facing a Live Reload infinite loop behavior when using Quarkus + Quinoa in a project structured as a monorepo.

Summary of the setup:

• Our project follows a monorepo structure under src/main/webui, with multiple packages inside packages/*.
• We use wireit and Vite to build one of the packages (packages/application).
• The front-end build process outputs a build/ or dist/ folder located within the monorepo structure (src/main/webui/packages/*) .
• Our configuration points quarkus.quinoa.ui-dir to the root of the front-end (src/main/webui) and quarkus.quinoa.build-dir to the location where Vite outputs the build.

Observed problem:

• Even with quarkus.quinoa.build-dir properly configured, Quinoa does not seem to automatically ignore this folder during Live Reload monitoring in dev mode.
• Every time Vite generates new files in the build output (build/), Quinoa detects changes — causing an infinite reload loop.
• This issue arises mainly because, in a monorepo, the build folder is not located directly at the root of the ui-dir, but deeper inside the structure (packages/application/build).
• The bundler’s configuration (Vite, via vite.config.js) defines the outDir, but it is independent of Quinoa’s configuration. It appears that Quinoa does not cross-reference this information when determining which directories to watch.

Main questions:

• Does Quinoa currently take quarkus.quinoa.build-dir into account when monitoring files for Live Reload in dev mode?
• If not, would it make sense for Quinoa to automatically ignore this folder (if it’s under ui-dir) to avoid Live Reload loops when local builds are present?
• For monorepo projects, where builds output to subdirectories like packages/*/build, is there any official recommendation or best practice to prevent this issue without needing to restructure the project?

Additional context:
We managed to work around the problem by pointing ui-dir directly to the final package (packages/application) and setting build-dir to build (a direct child folder of this package). This way, Vite's build output remains outside the monitored tree — but this is only a workaround, and it does not scale well if we need to watch changes in adjacent packages or rely on builds located in lower-level folders.

[melloware]

Your proposal sounds reasonable to me to try and ignore that folder from Live Reload. Let me see if it's possible as the whole folder is marked for live reload I believe. So you need a sub folder ignored of a parent folder than is being monitored.

[haikalrios]

Sure! Let me try to reproduce it in a simple standalone Quarkus project and open a ticket with all the details.

I’ll follow up shortly!

[melloware]

OK just let me know.

[melloware]

any luck?

[haikalrios]

No luck yet, but I haven’t given up 😁.

When I simplified the project and removed all extra dependencies, I used the Quinoa counter example and placed it into the same monorepo structure with wireit, where I originally had the issue — and the reload loop didn’t happen. Now I’m adding the dependencies back one by one to try to isolate the root cause.

[melloware]

OK keep plugging away!