Summary
In this chapter we set up the last piece in our "optimized workflow" puzzle. We learned what Source maps are and what problems they're designed to overcome. Problems such as having to manually find the line of SCSS among dozens of files because your browser only shows you the filename and line number of the CSS file. Or needing to copy and paste the changes you make in the browser to your text editor and save them there to make changes permanent.
We looked at setting up support for source maps in Firefox and Chrome and the slight differences between those. Mainly workspaces to sync an entire folder as opposed to Firefox's method of only syncing files as you save them.
We looked at how to solve an issue which can arise if you do not tell BrowserSync to be more selective about the files it watches. By default, BrowserSync will try match a file to a linked file in your HTML. If it finds a matching file it simply updates that one file and "injects" the changes. However, when it finds files...
