Earlier there were posts regarding how to build AMD modules with RequierJS and MS Build. Changes were needed to MS Build because there was no direct support from Visual Studio. The MS Build triggered NodeJS to complete the build process and copied required files to the output directory or deployment folder.
Why do we need client side build?
Most of client side libraries are written in JavaScritps and maintained in open source environments. These environments may not necessarily compatible with .NET and Visual Studio. As typical .NET developers we are used to with NuGet packages where we maintain .NET based packages. JavaScritp based packages are available in NuGet too but they are just an extension of the original open source packages. Someone has to volunteer to build NuGet packages. Therefore, it is possible that these packages may not be up to date. Wouldn't it be nicer if we could directly interact with those packages directly instead of getting them through NuGet?
Additionally, good practices such as AMD (asynchronous module) requires modules to be created and served in a certain a way. That includes concatenation of certain modules, minification and cleaning of the modules etc. Essentially it is similar to gathering certain C# files available in a project and creating a DLL by putting them altogether. Moreover, it should not minify when it is in debug/development mode but do it when it is a time for a deployment.
-- My apology for leaving the post incomplete; something has to be tacked on a priority; I will be back to complete the post as soon as possible; please come again after a few days to read the completed post; thank you --