<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->
<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->
<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->
## Current Behavior
<!-- This is the behavior we have today -->
## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
Fixes #
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->
<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->
<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->
## Current Behavior
<!-- This is the behavior we have today -->
The onboarding message during `create-nx-workspace` is not ideal.
## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->
We are A/b testing some options for the `create-nx-workspace` onboarding
message.
## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->
Fixes #
* feat(core): detect package manager used to invoke create-nx-(plugin|workspace)
When consumers create a new Workspace (or Plugin) using the create-nx-workspace (or
create-nx-plugin) generator, the package manager used to invoke the generator will be detected and
used as packageManager. For example: pnpx create-nx-workspace will use pnpm, yarn create
nx-workspace will use yarn. Explicit `--packageManager` flag will be priority over the detection.
* cleanup(core): reassign SELECTED_PM after each test run
* fix(core): augment args instead of hardcode --packageManager flag
* cleanup(core): use packageManagerLockFile instead of magic strings
* cleanup(core): fix typo in create-nx-workspace
* cleanup(core): ensure new workspace name for every test
* feat(core): detect package manager used to invoke create-nx-(plugin|workspace)
When consumers create a new Workspace (or Plugin) using the create-nx-workspace (or
create-nx-plugin) generator, the package manager used to invoke the generator will be detected and
used as packageManager. For example: pnpx create-nx-workspace will use pnpm, yarn create
nx-workspace will use yarn. Explicit `--packageManager` flag will be priority over the detection.
* cleanup(core): reassign SELECTED_PM after each test run
* fix(core): augment args instead of hardcode --packageManager flag
* cleanup(core): use packageManagerLockFile instead of magic strings
* cleanup(core): fix typo in create-nx-workspace
* cleanup(core): ensure new workspace name for every test
* fix(core): move detectInvokedPackageManager off of tao
Co-authored-by: Chau Tran <ctran@Chaus-MacBook-Pro.local>
* cleanup(core): normalized usage of fs-extra and updated fs-extra
* cleanup(misc): use fs over fs-extra when possible
Co-authored-by: Jason Jean <jasonjean1993@gmail.com>
* Simplify the determination & detection of the desired package manager.
* Add the `package-manager` option on plugin creation.
* Nx Cloud installation uses the appropriate package manager.
when creating plugin through npx create-nx-plugin, it fails by throwing error
Collection @nrwl/workpsace cannot be resolved
this commit changes the collection arguments pointing to proper path of the
module in tmp directory
