tree 4a037aeb89a4da6ea89dfa77c93b80959eb905e3
parent 10870103c0d2a58ce0d8b91cf14053dd0c315b20
author Raphael von der Grün <raphinesse@gmail.com> 1530203267 +0200
committer GitHub <noreply@github.com> 1530203267 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJbNQyDCRBK7hj4Ov3rIwAAdHIIAHZf7I5sIFZHuq83KDYJAVI8
 81JSxkufFc5wq80leGwIEtG2gpxtK9SKSI3SUPaSFLcVYfdGOS/KsxEGFDL9eHV7
 czoNeCF4vSZnRHNCTH1HUgucGofvhRj74nO7UlCUizfD4mYDmOs9ZBgJQjSRLhq5
 jTfhbmIO8WPwINl3jjRIZ8tbHfS4BLkSlJJ68egEqY4uHJkc0+EKF/rMgbkQINMJ
 13Jmdryr1klDJ7VuuJ4f9neM3Fv719gKJytxes+OQOO5m10TN5ceXPoI6N/xN1AR
 HiowFdJpQmQFcBs+3R2c7uBGGOrJuwJOQn+dDlGT2Y7DJSHxI9x0/idD7yKk2og=
 =DoFP
 -----END PGP SIGNATURE-----
 

CB-14173 Fix cordova <platform|plugin> add --link (#26)

This drops support for the untested and undocumented `link` option
which when set, caused `npm link` to be run instead of `npm install`.
However, the installed package's name cannot be extracted from the
output of `npm link`. Thus we failed in that case.

Now we always run `npm install` instead. This works for the use case of
`cordova <platform|plugin> add --link` since packages identified by a
local path are installed as symbolic links by npm.