Split up generator-donejs

I suggest we separate generator-donejs into separate generators:

• donejs-app
• donejs-plugin
• donejs-generator
• donejs-component
• donejs-supermodel
• donejs-module

and a utility project donejs-plugin-utils (or something like that) for the utility functions currently in lib/utils.js.

The main benefit of this is that dependencies that are only needed by one of the generators would not need to be installed with donejs add app. Here’s a list of those dependencies:

generator	dependency	size
component	can-view-autorender	570 KB
component	done-component	1.9 MB
component	can-component	1.8 MB
supermodel	can-fixture	3.9 MB
supermodel	can-connect	3.8 MB

Install times before removing these:

Analyzing 22 dependencies...
...
Total time (non-deduped): 2m 5.7s
Total size (non-deduped): 175 MB

And once they’re removed:

Analyzing 17 dependencies...
...
Total time (non-deduped): 1m 50.9s
Total size (non-deduped): 163 MB

Another benefit of doing this is that it would make the donejs-cli code a bit more maintainable because it would remove the special casing for generator-donejs and these generators would be added just like anything else using donejs add.

[phillipskevin]

What if your app is only using donejs-custom-elements? Or donejs-react-view-models?

Obviously, these don’t exist, but it’s possible a year from now that someone using DoneJS would not need can-component.

I don’t see a problem with installing can-component when you run donejs add component.

[frank-dspeed]

@phillipskevin when the generator-donejs gets splitted and ssr would be optional we still could ask on donejs add app if he wan’ts to use ssr or not and if yes simply npm install that also