Why disable caching in Chrome to see changes in JS files served from IIS?

I spent some time troubleshooting why after setting “Output cache” settings in IIS to “prevent all caching” my JavaScript files were not being reloaded when the page is refreshed. It turned out that I had to disable caching from within the Chrometools network tab.
My question is why, as this has never been necessary when using development servers in webpack, gulp, live-server etc unless loading identical resources?