Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(core): migrate using yarn when nxJson has another package manager configured #16844

Merged
merged 1 commit into from
May 7, 2023

Conversation

johnhwhite
Copy link
Contributor

nx test nx now tests the detectPackageManager function

Current Behavior

nx migrate --run-migrations uses yarn despite nx.json configuration.

Expected Behavior

nx migrate --run-migrations should respect nx.json configuration.

Related Issue(s)

Fixes #16836

… configured

`nx test nx` now tests the `detectPackageManager` function

Fixes nrwl#16836
@vercel
Copy link

vercel bot commented May 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2023 3:54pm

@AgentEnder AgentEnder merged commit 0654776 into nrwl:master May 7, 2023
FrozenPandaz pushed a commit that referenced this pull request May 8, 2023
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nx migrate latest is looking for yarn even though npm is specified
2 participants