Chrome/Vivaldi has the best set of developer tools of the available browsers in the labs, so we will be using this as the primary browser for developing the web site. Vivaldi (which is what we use in the Linux lab) is base on Chrome.
Hit <> in Chrome/Vivaldi to bring up the developer tools.
Click somewhere inside the developer tools pane to give it focus, and hit <> to bring up the settings.
In the <> section, untick <> and <>. Source maps allow the tools to work with minified code. We won't be using minification and having these settings enabled means that Chrome will be asking our server for a bunch of map files that we don't have which will cause a lot of 404 errors to appear in the output. This is annoying, so we are disabling it.
If you are wondering what minification is, it is when the code is processed to shrink all of the variable and function names and all unneeded white space is removed. This significantly reduces the amount of bandwidth required to send the files overs the internet, but makes them unusable to developers. Map files effectively allow the developer tools to reverse the minification process. Our code is not minified, so we don't need to use map files.
In the <> section, tick <>. We don't ever want to be testing our system using cached versions of files that don't include our most recent changes.
So long as we have the developer tools open we now know that we will always be looking at the latest versions. You should get into the habit of keeping the developer tools, and more specifically the console open. This allows you to see any errors that occur, in addition to disabling the cache.
Under the <> section, tick <>. We will be doing a lot of client-side redirection so we don't want the messages to vanish every time the browser is redirected to a new page.