I have done some searching and seen this issue here: Source Maps being written twice · Issue #1386 · roots/sage · GitHub but it sounds as if it should be resolved in the latest version of Sage. I finally upgraded from Sage 8.0.0 to 8.2.1 and have now run into this issue. I have deleted node_modules and re-ran npm install. No errors from gulp. I have tried both injecting the font-awesome.scss into the build by editing bower.json (so wiredep will include it in main.scss), and just letting it reference the css file directly. When I have the font-awesome.css file loaded from bower_components, all my styles point to font-awesome.css:4 in Chrome dev tools. When I have it included in main.scss styles point to font-awesome.css:1. It is quite strange. I have the feeling I am just missing something since I did quite a lot of merging today to get up to 8.2.1 but I cannot think what it might be. Any ideas?
Also this is a development site hosted locally with bedrock-ansible, so WP_ENV is indeed being set to development. And main.css.map is being created in the dist/styles folder.
/*# sourceMappingURL=main.css.map */ Is located in the last line of main.css