After a long time of unreliable results with Web Compiler, especially in TFS, I decided to replace it with node-sass.
Web Compiler is an extension to Visual Studio that listens to changes in your .scss files (among others) and compiles them. It can also be configured to run as part of your TFS build. With our solution this has however been highly unreliable, where Web Compiler claims that files have been compiled, but the changes you made are not reflected in the resulting bundles. This has caused extra work in our team of about 15 developers, where a bug fix you made is overwritten by some other change and not included in the CSS bundle in the integration environment the next day.
Since I hadn’t got the impression that this was a big issue for other team members in our local development environment, I decided to keep Web Compiler in Visual Studio and use its compilerconfig.json as configuration for which bundles to create. In reality we have quite a few more bundles for different parts of the application, so that was also a reason to keep the existing configuration.
This is more of a quick hack than well-crafted code, but it has turned out to work great. Now I can rely on my changes to reach the integration and test environments after the next nightly deploy.