Open jamesstar89 opened 7 years ago
I have the same issue. {cache: false}
does not seem to work
Cache seems to be associated with the isAbsolute template path?
@amitport done a quick work around...
Updated following lines in package index.js
var uniqueName = name + uuid(); cb(null, dust.loadSource(dust.compile(data, uniqueName || file)));
Might do a PR later on, but just caching the name as a unique name will let you see changes immediately without the server reload.
Do you need to restart server each time you want to make an update to a dust template?
Thanks.