title: Is it necessary to rename .js files to invalidate cache?
body: <p>I want to invalidate cached app.js after every single release.</p>
  
  <p><strong>Short question</strong>:</p>
  
  <p>Is it necessary to physically rename(by <a href="https://github.com/sindresorhus/gulp-rev" rel="nofollow">gulp-rev</a>, for example) <code>app.js</code> to <code>app-a23ds.js</code> every time or is enough to add param with hash in html like <code>app.js?_=&lt;build number&gt;</code></p>
  
  <p><strong>Description</strong>:</p>
  
  <p>I was sure before that is enought to write something like <code>app.js?_=&lt;build number&gt;</code> in  index.html to load new file instead of cahed. But when I'm investigate this question deeper I found a few of huge solutions for this case. Like <a href="https://github.com/sindresorhus/gulp-rev" rel="nofollow">gulp-rev</a>. The main idea of them is to write a new file with new filename (old filename + revisions hash). Is it really neccessary or what?</p>