Vite Rebuild doesn't work for source/_assets/css/main.{js,css}

[tomasnorre]

I have a problem with my Jigsaw blog after switching to version 1.8 and Vite. Changes in source/_assets/css/main.js nor source/_assets/css/main.css doesn't trigger a Vite rebuild nor a Hot Reload of the page.

I have tested with both a site setup with vendor/bin/jigsaw init and vendor/bin/jigsaw init blog neither of them works, therefor I have added the issue here directly.

Steps to reproduce:

mkdir -p /tmp/jigsaw-vite
cd /tmp/jigsaw-vite
composer require tightenco/jigsaw
vendor/bin/jigsaw init
# start the two servers
vendor/bin/jigsaw serve
npm run dev

Now make a change in source/_assets/css/main.js or source/_assets/css/main.css and see that the rebuild doesn't happen, nor the reload. If I do a change in source/index.blade.php or source/_layouts/main.blade.php then it rebuilds and reloads as expected, but not the two css or js files.

If the problem comes from the @tighten/jigsaw-vite-plugin I cannot say yet.

Let me know if I can help you in any what to get this solved, I'm not really a frontend kind of person, but will support the best I can.

[tomasnorre]

I don't know if it's the right fix, but following in https://github.com/tighten/jigsaw-vite-plugin/blob/main/src/index.ts#L110

const defaultWatchFiles = (source) => [
  "config.php",
  "bootstrap.php",
  "listeners/**/*.php",
  `${source}/**/*.md`,
  `${source}/**/*.php`,
+ `${source}/**/*.js`,
+ `${source}/**/*.css`,
  `${source}/**/*.html`
];

Solves the problem for me.

[tomasnorre]

If I add following top my vite.config.js to following

import { defineConfig } from 'vite';
import jigsaw from '@tighten/jigsaw-vite-plugin';
import tailwindcss from '@tailwindcss/vite';

export default defineConfig({
    plugins: [
        jigsaw({
            input: [
                'source/_assets/js/main.js',
                'source/_assets/css/main.css'
            ],
-            refresh: true,
+            refresh: {
+                files: [
+                    'config.php',
+                    'bootstrap.php',
+                    'listeners/**/*.php',
+                    'source/**/*.md',
+                    'source/**/*.php',
+                    'source/**/*.html',
+                    'source/**/*.css',
+                    'source/**/*.js',
+                ],
+                ignored: [
+                    'build_**/**',
+                    'cache/**',
+                    'source/**/_tmp/*',
+                ],
+           },
        }),
        tailwindcss()
    ],
});

Then it works for me.

I don't know if that's the intention to add those manually? I would expect it to be default behavior that source/**/*.css and source/**/*.js also would trigger a rebuild and reload.

[gcavanunez]

@tomasnorre we shouldn't need to specify *.js or *.css - know a lil while back we ran into issues with the hot file jigsaw uses to detect dev mode causing issues however we resolved it on the 1.0.1 for @tighten/jigsaw-vite-plugin

I did tried to reproduce the error, however was unable to

Attemp reproduce

jigsaw-debug.mp4

I would note that, when using the vendor/bin/jigsaw serve- we'd want to run this after having had started the vite dev server npm run dev else jigsaw wouldn't be able to properly inject the appropriate assets

[tomasnorre]

I'll have to look into it again. I have used the work around since. So would have to test again.

[tomasnorre]

Thank you so much for the effort on trying to visualize this. I have made a small video too.

I cannot make it work like you do.

As you see. The change in CSS directly doesn't trigger a hot-reload, but the in the layouts blade file does.

I'm on Ubuntu Linux, not that I think it matters in this context.

Screencast.From.2025-09-22.08-02-24.mp4

[gcavanunez]

thank you so much for the recording!! was able to re-create the issue!

it seems to be related to these config settings we enforce on the plugin that prevent double watching behavior. it's also odd that it seems to be OS specific which opens up it potentially also being an issue upstream on either vite or chokidar

All that said we are still exploring the appropriate solution given that assets ideally don't need to be re-registered explicitly in the way we treat non-asset files.

[tomasnorre]

@gcavanunez thanks for getting back on this. Let me know if I can help in any way, with testing, fixing, what ever. Don't have an idea myself, right now, how to solve it, but would be happy to help any way possible.

Just let me know if my assistance is needed.