search

nrwl / nx

Smart Monorepos · Fast CI
https://nx.dev
MIT License
23.29k stars 2.32k forks source link

create-nx-workspace should respect angular-cli's package manager default configuration #534

Closed cvgaviao closed 6 years ago

cvgaviao commented 6 years ago

in angular-cli v6 we can set the default package manager using:

ng config -g cli.packageManager <yarn | npm>

so we don't need to specify which one to use when using ng new

would be great not to have to specify that parameter every time with create-nx-workspace also.

jschwarty commented 6 years ago

@cvgaviao With the latest version of Nx (v6) it is possible to create new Nx workspaces using the ng new command instead of the create-nx-workspace binary (see Getting Started for more info). This follows the Angular CLI workflow so it should honor the config setting. We are keeping the create-nx-workspace binary around just in case but don't currently plan on adding to it since we are now able to leverage the ng new command.

ng new myworkspacename --collection=@nrwl/schematics
cvgaviao commented 6 years ago

@jschwarty, thanks for the return.

cvgaviao commented 6 years ago

@jschwarty, I noted that ng new myworkspacename --collection=@nrwl/schematics is creating a project using versions of @angular/compiler-cli (6.0.1) that is not the current (6.0.7) installed in my environment.

Also, calling yarn ng update do not offer any update.

Wouldn't be possible to the ng new provided by nx collection to copy versions from the collection provided by the current installed angular-cli ?

github-actions[bot] commented 1 year ago

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.