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): use nx@next when migrating to next #16557

Conversation

AgentEnder
Copy link
Member

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #

@vercel
Copy link

vercel bot commented Apr 25, 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 Apr 26, 2023 9:36pm

@AgentEnder AgentEnder force-pushed the fix/use-next-for-migrate-when-migrating-to-next branch from 8de78e5 to 2badf11 Compare April 25, 2023 21:04
Comment on lines 1026 to 1028
function nxCliPath(
version = process.env.NX_MIGRATE_USE_NEXT === 'true' ? 'next' : 'latest'
) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a weird function name, can we change it to like... installNxTemporarily(version: 'latest' | 'next')?

Don't make it optional, and move the environment variable check outside of here.

@github-actions
Copy link

github-actions bot commented May 2, 2023

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 2, 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.

2 participants