Experience with Grunt on large projects

Question

JavaScript

Can anyone share their experience of using Grunt on large projects?

A project on .Net with a huge number of unique pages, 5-50 js are connected on each.
It is planned to collect for each page its own js-file from all the scripts that are used on it.
The task is complicated by the presence of a large number of dependencies. For example, you need to connect some module, but it needs some libraries or jquery plugins. And tracking it manually is not possible.

Another question is how to organize the assembly of the project in the development environment and in production?
In production, you need to merge and minify all files, and in development, you need to include them all separately. But store all the information about what scripts are needed and with what dependencies you want in the form of configs in json files.

Where can I read about best practice? The search produces mostly very simple tutorials for beginners.

Answer 1

Bower can help with dependencies.
There is yeoman.io/ which uses Grunt (and many of its plugins) and Bower.

Answer 2

For dev just not needed

Answer 3

Isn't it easier to use require.js? The problem of building for dev and prod, resolving dependencies and generally managing the code is immediately solved.

Answer 4

github.com/serheyShmyg/requirejs-jquery-backbone