Idea: Option to move 'core' packages to contrib at 'mean init'

[manojchandrashekar]

I installed mean 0.6.1 for a new project and having used the 0.5.5 until now, the changes were somewhat overwhelming. The major change was that the 'core' packages were now part of node_modules. I rely much on what these packages do and almost always extend the functionality by modifying these files.

Is it worth having an option during 'mean init' that asks the developer if he wants these packages to be present in packages/contrib and if so, do the following:

1. Move the meanio-* packages to packes/contrib/
2. Remove their dependency from package.json
3. Remove the reference to packages/contrib from .gitignore
4. Show a warning to the developer that upstream changes to these packages cannot be updated automatically and have to be patched manually from http://github.com/linnovate

P.S.: Currently, the mean-cli changes the package directory name to the app name from the cmd prompt, however the package name is still meanStarter. Is it not possible to replace the package name to the app name as well? (I'll try to submit a PR for this, when I get time)