cssify should be a dependency in the plugin generator

[matthewp]

When browserify crawls through package.jsons it looks for "browser": "transforms" [ ] and applies those transformations. In order to find cssify, it needs to be a dependency of the project, not a devDependency.

We should either remove cssify from the generator or make it a project dependency.

[matthewp]

Needs to be a dependency, removing it would be a breaking change and not interested in dealing with that right now.

[phillipskevin]

should we remove it as a dependency for 1.0?

[matthewp]

I don't know, maybe there should be a --css flag. I guess if you are writing a widget that includes css you'd want it for browserify users.

[pYr0x]

Can we ask the user with a prompt if he would reuse the widget with browserify?

[matthewp]

We could do some type of prompt, yeah. I wonder if it should be phrased as "Does this project use CSS" or something to that effect.

[justinbmeyer]

I'd keep it for 1.0. Easy enough to delete later.

[phillipskevin]

There is a PR open to make it an opt-in if we want to use that: #136

cc @leoj3n