What does `npm i -g cordova-plugin-device` do? Just because things are similar does not mean you should force them to be the same. I don't really see a benefit in doing this though, and I think we are going to end up with circular unresolvable dependencies. or at least greatly increased complexity in dependency resolution.
Having 2 ways to do things just makes it harder for us .... Thinking outloud ... isn't the post install really just something like: ../../cordova plugin add npm_modules/cordova-plugin-device/ That assumes no dependency resolution ... which would make it explode. Overall, I don't think the feature is worth the complexity it would add, and I don't even think it makes things easier for users. What is the benefit of typing 'npm i cordova-plugin-device' vs 'cordova plugin add cordova-plugin-device' ? Character count? @purplecabbage risingj.com On Mon, Mar 9, 2015 at 5:36 PM, Steven Gill <stevengil...@gmail.com> wrote: > I think it is worth exploring a generic post install script plugin authors > could include that would install the plugin into a cordova project after a > npm install. I haven't had any time to actually explore this yet though. > > My initial reaction was that it would be hard to get right. After some > thought and discussion with the npm people & Anis, it might be a really > nice way of doing it. > > It would be pretty sweet if people could just go `npm i > cordova-plugin-device` and have it install the plugin into their cordova > projects. > > The script would have to: > * detect if it is a cordova project and what version > * do everything plugin install does now > > Just wanted to collect some feedback, advice, and concerns people have > before I attempt to build it. >
