-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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(nextjs): handle buildable libs correctly #15795
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d39df2c. 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. |
6ef47f2
to
d39df2c
Compare
@@ -134,7 +134,7 @@ export function withNx( | |||
} = getNxContext(graph, originalTarget); | |||
const projectDirectory = projectNode.data.root; | |||
|
|||
if (!options.buildLibsFromSource && targetName) { | |||
if (options.buildLibsFromSource === false && targetName) { |
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.
This is the fix, because we're not getting the default value from schema.json
so we need to check if it is explicitly set to false
, not just falsy.
(cherry picked from commit 63cdddf)
(cherry picked from commit 63cdddf)
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. |
The method to determine incremental builds is broken. This PR patches that logic.
Current Behavior
Buildable libs cannot be consumed unless it is built.
Expected Behavior
Buildable libs should build from source unless
--buildLibsFromSource=false
is passed.Related Issue(s)
Fixes #15785