jwarby / grunt-unified-manifest Goto Github PK

As noted in issue #1, using CLI tools such as npm and bower for installing packages is going to be a bit of a headache, as the task will overwrite any changes made in the generated manifest files.

I am wondering if this whole concept would be better suited as a generator for the Yeoman ecosystem, as Yeoman has some nice built-in functionality for handling conflicts in files.

I will do some more research, and if viable, a proof-of-concept of this idea to see if it works any better.

Keys like dependencies, devDependencies, peerDependencies, etc, should probably be merged instead of getting completely overwritten when the task runs.

The current setup means you can't use CLI tools such as npm and bower to install a package and save it to the manifest, as it will just get overwritten when the task runs.