Skip to content

fix(core): derive graph node type correctly when projectType is not set #32018

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

Merged
merged 2 commits into from
Jul 25, 2025

Conversation

leosvelperez
Copy link
Member

Current Behavior

When building the project graph nodes, the node type is always inferred as lib when projectType is not set.

Expected Behavior

When building the project graph nodes, the node type should be derived correctly using the same logic used by generators when projectType is not set.

Related Issue(s)

Fixes #31983

@leosvelperez leosvelperez self-assigned this Jul 22, 2025
@leosvelperez leosvelperez requested a review from a team as a code owner July 22, 2025 11:17
@leosvelperez leosvelperez requested a review from AgentEnder July 22, 2025 11:17
Copy link

vercel bot commented Jul 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview Jul 24, 2025 3:57pm

Copy link
Contributor

nx-cloud bot commented Jul 22, 2025

View your CI Pipeline Execution ↗ for commit 2ad334a

Command Status Duration Result
nx nx-release @nx/nx-source --parallel 8 --loca... ✅ Succeeded 4m 25s View ↗
nx run-many -t build-native-wasm ✅ Succeeded <1s View ↗
nx run-many --target=build-native -- --target=a... ✅ Succeeded 4m 44s View ↗
nx run-many --target=build-native -- --target=a... ✅ Succeeded 4s View ↗
nx run-many --target=build-native -- --target=a... ✅ Succeeded <1s View ↗
nx run-many --target=build-native -- --target=x... ✅ Succeeded <1s View ↗
nx run-many --target=build-native -- --target=x... ✅ Succeeded 1s View ↗
nx run-many --verbose --outputStyle stream --ta... ✅ Succeeded <1s View ↗

☁️ Nx Cloud last updated this comment at 2025-07-24 15:38:15 UTC

Copy link

🐳 We have a release for that!

This PR has a release associated with it. You can try it out using this command:

npx create-nx-workspace@0.0.0-pr-32018-c6ab05e my-workspace

Or just copy this version and use it in your own command:

0.0.0-pr-32018-c6ab05e
Release details 📑
Published version 0.0.0-pr-32018-c6ab05e
Triggered by @leosvelperez
Branch fix/issue-31983-wrong-project-type
Commit c6ab05e
Workflow run 16442745840

To request a new release for this pull request, mention someone from the Nx team or the @nrwl/nx-pipelines-reviewers.

Copy link

🐳 We have a release for that!

This PR has a release associated with it. You can try it out using this command:

npx create-nx-workspace@0.0.0-pr-32018-1ec2cae my-workspace

Or just copy this version and use it in your own command:

0.0.0-pr-32018-1ec2cae
Release details 📑
Published version 0.0.0-pr-32018-1ec2cae
Triggered by @leosvelperez
Branch fix/issue-31983-wrong-project-type
Commit 1ec2cae
Workflow run 16474308657

To request a new release for this pull request, mention someone from the Nx team or the @nrwl/nx-pipelines-reviewers.

@leosvelperez leosvelperez force-pushed the fix/issue-31983-wrong-project-type branch from 1ec2cae to f7d8443 Compare July 24, 2025 13:30
@leosvelperez leosvelperez requested a review from a team as a code owner July 24, 2025 13:30
@leosvelperez leosvelperez force-pushed the fix/issue-31983-wrong-project-type branch from b5b74c7 to 2ad334a Compare July 24, 2025 15:04
Copy link

🐳 We have a release for that!

This PR has a release associated with it. You can try it out using this command:

npx create-nx-workspace@0.0.0-pr-32018-2ad334a my-workspace

Or just copy this version and use it in your own command:

0.0.0-pr-32018-2ad334a
Release details 📑
Published version 0.0.0-pr-32018-2ad334a
Triggered by @leosvelperez
Branch fix/issue-31983-wrong-project-type
Commit 2ad334a
Workflow run 16500916903

To request a new release for this pull request, mention someone from the Nx team or the @nrwl/nx-pipelines-reviewers.

@leosvelperez leosvelperez merged commit b5b4cd5 into master Jul 25, 2025
19 checks passed
@leosvelperez leosvelperez deleted the fix/issue-31983-wrong-project-type branch July 25, 2025 12:13
jaysoo pushed a commit that referenced this pull request Jul 25, 2025
… set (#32018)

## Current Behavior

When building the project graph nodes, the node `type` is always
inferred as `lib` when `projectType` is not set.

## Expected Behavior

When building the project graph nodes, the node `type` should be derived
correctly using the same logic used by generators when `projectType` is
not set.

## Related Issue(s)

Fixes #31983
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Typescript references inference unstable/doesn't always work
3 participants