[Bug]: Post-Update Regression - React/Vite Fails Without "Static Site" Ticked, Leading to MIME Type Error

[xzhashi]

Error Message and Logs

Following a recent update (version needed), my React/Vite Single Page Application (SPA) deployed via Coolify now fails to deploy or run correctly unless the "Static Site" checkbox is explicitly ticked.

Prior to the update, I was able to deploy the application with client-side routing (React Router) without any extra build steps, as Coolify correctly configured the underlying web server (Nginx/Caddy) for SPAs.

The current behavior presents a Catch-22:

"Static Site" Ticked (Current Forced Workaround): The application deploys quickly, but sub-routes (like /dashboard) fail on refresh with the Nginx 404 error (as the server is not configured to fall back to index.html).

"Static Site" Unticked (Correct SPA Mode): The deployment process takes hours and often results in a MIME type error (Failed to load module script: Expected a JavaScript-or-Wasm module script but the server responded with a MIME type of "text/plain"), indicating the web server is incorrectly serving the bundled JavaScript assets.

Expected Behavior

The application should deploy successfully with the "Static Site" option unticked (to enable SPA routing) and the deployed web server should correctly serve all bundled JavaScript/Module files with the MIME type application/javascript (or text/javascript).

Steps to Reproduce

Use a standard React application built with Vite (using npm run build to create a dist folder).

In Coolify, configure a new resource for the application, ensuring:

    Build Tool: Nixpacks is used.

    Build Command: npm ci && npm run build

    Output Directory: dist

    Static Site: Unticked/Disabled.

Initiate deployment.

Observe the long build time, followed by the MIME type error in the browser console upon attempting to load the site.

Example Repository URL

No response

Coolify Version

v4.0.0-beta.440

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

[coderabbitai]

Caution

The CodeRabbit agent's plans did not produce any file changes.

[djsisson]

if this is a spa, arent you supposed to tick, is static site, and with SPA ticked,

static site is required to bundle your image with nginx
SPA is required so everything goes to index.html, not a different path, as in SPA no other paths exist server side

[xzhashi]

sorry its not SPA

[djsisson]

if youre using react router, its a spa?

[xzhashi]

Yes,
but the main issue is without ticking static it was working till yesterday
Now this issue raised after the new update
One of my friend with his nextjs project he is facing same

[djsisson]

i'm assuming this was bugged before, you should have always had to tick static with spa before, since this is what you are deploying

a nextjs project uses ssr, so has no intermediate nginx, so i can't see how they can have the same error

[andrasbacsai]

@xzhashi Can you please make a small simple repository that has the same issue (or share yours if its not private) so I can reproduce it?

[xzhashi]

@xzhashi Can you please make a small simple repository that has the same issue (or share yours if its not private) so I can reproduce it?

Yes ill try, so before this update we never ticked the static site we just let the nixpacks and we used to deploy directly but now for every application we are ticking static site to make sure the mime/type error wont come

[brdtheo]

I had a similar issue when deploying Vite with Nixpacks. The container deployed and ran successfully but it looks like after the updates, the nixpacks deployment configuration were altered and the publish directory setting has been reset to / instead of /dist.
I don't know if it can be related.

[Nikseell]

Had same issue where site showed MIME Type error. Fixed by adding in env file

NIXPACKS_SPA_OUTPUT_DIR=build

[saitobp]

Having the same issue, before version 440 everything was working normally, some things that I've noticed, all my env vars were gone

• Tried ticking the static page (never had to do it before for vite with react-router) did not work
• Tried ticking the static page + spa, also did not work
• Tried adding /dist to publish directory, also did not work
• Tried adding NIXPACKS_SPA_OUTPUT_DIR=build, did not work
• Tried creating a new enviroment after 440, with static site + spa, this worked, also noticed that there was a new env of NIXPACKS_NODE_VERSION=22, adding this to the original project that was breaking make it work

Final config was for the old project static + spa + /dist on publish directory + new env var NIXPACKS_NODE_VERSION=22