Open jjaimealeman opened 2 years ago
I think the problem lies here:
Specifically, returning []
skips any further processing, meaning that postcss (hence tailwind) isn't triggered at all.
I'm not sure how handleHotUpdate
should look exactly, but a workaround is to remove it entirely:
// TODO: remove once https://github.com/alexlafroscia/vite-plugin-handlebars/issues/192 is resolved
function handlebarsOverride(options) {
const plugin = handlebars(options);
// Currently handleHotUpdate skips further processing, which bypasses
// postcss and in turn tailwind doesn't pick up file changes
delete plugin.handleHotUpdate;
return plugin;
}
plugins: [
handlebarsOverride({ ... }),
],
didn't help when simple HTML partial changes
I think the problem lies here:
Specifically, returning
[]
skips any further processing, meaning that postcss (hence tailwind) isn't triggered at all.I'm not sure how
handleHotUpdate
should look exactly, but a workaround is to remove it entirely:// TODO: remove once https://github.com/alexlafroscia/vite-plugin-handlebars/issues/192 is resolved function handlebarsOverride(options) { const plugin = handlebars(options); // Currently handleHotUpdate skips further processing, which bypasses // postcss and in turn tailwind doesn't pick up file changes delete plugin.handleHotUpdate; return plugin; }
plugins: [ handlebarsOverride({ ... }), ],
reloadOnPartialChange: true,
added tovite.config.js
but it makes no difference.Any solutions ?