14 Commits

Author SHA1 Message Date
Charles Lyding
f4127b5b43 fix(@angular/cli): fully use add command registry option when installing packages
Fixes: #16766
2020-02-10 16:02:05 -08:00
Charles Lyding
0d6dae107d fix(@angular/cli): support path spaces with temporary package installs
Fixes: #16865
2020-02-10 16:02:05 -08:00
Alan Agius
08f0067145 fix(@angular/cli): fix package manager warnings when running temporary install
Related to: #16205
2019-11-18 10:27:47 -08:00
Alan Agius
1903dd5119 fix(@angular/cli): add pnpm options to install package task
Fixes #16149
2019-11-12 11:46:07 -08:00
Alan Agius
08c3959ee4 fix(@angular/cli): remove no-bin-links during npm/yarn install
Previously we passed `--no-bin-links` because we used to install packages globally in some cases. But now this is no longer needed as we should now have permissions to generate "local" bin links even during a temp installations as these  will no longer generate bin links in the global context.

Fixes #16133
2019-11-11 16:52:46 -08:00
Charles
b8257e276e fix(@angular/cli): re-introduce install package using shell spawn (#16112)
This works around a Windows CI failure that related to the PATH environment variable and a failure to located the `npm` command.
2019-11-08 07:54:47 -08:00
Alan Agius
f35b80ebaf fix(@angular/cli): use spawned process error when it's available
In some cases when an error occurs in the spawned process the `error` property will be populated instead of `stderr` or `stdout`.

See: https://nodejs.org/api/child_process.html#child_process_child_process_spawnsync_command_args_options
2019-11-07 10:07:10 -08:00
Alan Agius
c5ab958eb3 fix(@angular/cli): handle null stderr during npm install 2019-11-06 10:50:47 -08:00
Charles Lyding
84ba5d55f0 fix(@angular/cli): only show add/update package install output on errors
Closes #16014
Closes #16027
2019-11-05 16:30:14 -08:00
Alan Agius
8820093b7f fix(@angular/cli): don't install using global command but rather install in a different folder
Fixes: #16010
2019-11-04 13:24:57 -08:00
Alan Agius
548617ca4c fix(@angular/cli): updated CLI should not have analytics enabled
In the case users don't have analytics globally configured when the CLI will self update during ng update. It will prompt to configure this.

However, afterwards the update will fail with `Repository is not clean.  Please commit or stash any changes before updating.` as there would be uncommited local changed.
2019-10-29 20:21:51 -07:00
Alan Agius
936a9512ae refactor(@angular-devkit/build-angular): move around i18n methods to make them re-usable 2019-10-25 09:52:56 -07:00
Alan Agius
70e460d656 refactor: use require.resolve instead of custom resolve (#15906) 2019-10-23 09:59:36 -07:00
Alan Agius
b0dcfd08a0 fix(@angular/cli): logic to determine if the installed CLI is out of date
With this change we now check if the current CLI version is the latest published version. If it is not, we install a temporary version to run the `ng update` with.
2019-10-22 13:13:54 -07:00