The article details a developer's experience troubleshooting a caching issue in their Eleventy (11ty) setup using Vento as the templating language.The problem arose during local development when changes to JS files weren't reflected until the server was restarted.

The developer discovered that files in the '_includes/assets' folder were being ignored by the watch system, causing cached versions to persist.By modifying the Eleventy configuration to include a custom event callback for the 'eleventy.beforeWatch' trigger, they successfully updated the cache to reflect changes in both '_assets' and '_includes' directories.

The solution involved manipulating the cached file list as an object (passed by reference in JavaScript), allowing modifications to affect Vento's cache removal process.

The developer notes that this issue doesn't occur with CSS due to PurgeCSS's direct injection method, and concludes that the problem stemmed from their asset compilation workflow, which they've since resolved.