the method you mentioned to timestamp all js,css files doesn't matter to small websites, which perfectly solves the client-side caching problem. The side effect is that most of the js,css files are not changed at all, and the client is forced to reload the new version, which slows down the display speed of the page and is not recommended.
Evil
if you have to use it, you don't have to look for plug-ins everywhere. You can write a pathBuilder (filePath) template method by yourself. The purpose of this method is to add a timestamp to the incoming path. Then you call this method in the template file to introduce the js and css files. For example,

<srcipt src="{pathBuilder('../js/index.js')}"></script>

right path
using Webpack is a perfect labor-saving solution at present, because it can:

1. automatically compiles js and css files when they are released. The file name is the hash value of the file. The file content and hash value remain the same. The file name with hash value reflects the file version.
2. it can replace files that reference js and css and change them to the final real path (both js and css filenames are replaced).