fix(misc): init should prompt for cloud when using dot nx folder #30501
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
|
View your CI Pipeline Execution ↗ for commit 4b35bfe.
☁️ Nx Cloud last updated this comment at |
AgentEnder
force-pushed
the
fix/core-init-dotnx-cloud
branch
4 times, most recently
from
c3e349f to
52e54bd
Compare
FrozenPandaz
approved these changes
Mar 27, 2025
AgentEnder
force-pushed
the
fix/core-init-dotnx-cloud
branch
from
52e54bd to
4b35bfe
Compare
AgentEnder
added a commit
that referenced
this pull request
Mar 27, 2025
Some error handling is missing after #30501
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
When nx is installed in the
.nxdirectory the init flow is substantially different. This changes how some prompting works as well as how plugin installation flows.Expected Behavior
The two flows operate in a similar manner.
Related Issue(s)
Fixes #