-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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): parse project configs only in js #18009
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 159f749. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
eb8e908
to
178a461
Compare
178a461
to
1e5238d
Compare
1e5238d
to
8958f39
Compare
8958f39
to
bc56966
Compare
bc56966
to
159f749
Compare
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. |
Current Behavior
Nx parses config files in Rust.. and then reparses it in JS and sometimes assigns the project a different name.
Expected Behavior
Nx only identifies project config files in rust.. but only parses the file in JS and always assigns the project the same name. The project file map is calculated in JS from the parsed project configs.
Related Issue(s)
Fixes #