-
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
feat(devkit): allow updating package json based projects #27138
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 04cf256. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
18d8879
to
04cf256
Compare
|
||
const packageJson = readJson<PackageJson>(tree, packageJsonFile); | ||
|
||
if (packageJson.name === projectConfiguration.name ?? projectName) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the name is not equal, what do we do? Do we set it in package.json#name
or do we set it in package.json#nx.name
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nx.name, setting package.json name could break a published package
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
Calling
updateProjectConfiguration
on a package json based project failsExpected Behavior
Calling
updateProjectConfiguration
on a package json based project worksRelated Issue(s)
Fixes #26530