Skip to content

feat(nest): added @nx/nest/plugin with NestJS project detection through nest-cli.json#35551

Open
vrxj81 wants to merge 2 commits into
nrwl:masterfrom
vrxj81:feat/nest-plugin-entrypoint
Open

feat(nest): added @nx/nest/plugin with NestJS project detection through nest-cli.json#35551
vrxj81 wants to merge 2 commits into
nrwl:masterfrom
vrxj81:feat/nest-plugin-entrypoint

Conversation

@vrxj81

@vrxj81 vrxj81 commented May 3, 2026

Copy link
Copy Markdown
Contributor

Current Behavior

The @nx/nest plugin does not detect NestJS projects from nest-cli.json, so Nest applications configured that way are not picked up by the plugin.

Expected Behavior

The @nx/nest plugin detects NestJS projects through nest-cli.json.

Related Issue(s)

Refs #35503

@vrxj81 vrxj81 requested a review from a team as a code owner May 3, 2026 07:25
@vrxj81 vrxj81 requested a review from FrozenPandaz May 3, 2026 07:25
@netlify

netlify Bot commented May 3, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit a21b384

@netlify

netlify Bot commented May 3, 2026

Copy link
Copy Markdown

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit a21b384

@nx-cloud

nx-cloud Bot commented May 4, 2026

Copy link
Copy Markdown
Contributor

View your CI Pipeline Execution ↗ for commit 3053edd

Command Status Duration Result
nx affected --targets=lint,test,build,e2e,e2e-c... ✅ Succeeded 42m 18s View ↗
nx run-many -t check-imports check-lock-files c... ✅ Succeeded 2s View ↗
nx-cloud record -- pnpm nx-cloud conformance:check ✅ Succeeded 44s View ↗
nx build workspace-plugin ✅ Succeeded <1s View ↗
nx-cloud record -- nx sync:check ✅ Succeeded 14s View ↗
nx-cloud record -- nx format:check ✅ Succeeded 4s View ↗

☁️ Nx Cloud last updated this comment at 2026-06-05 19:19:44 UTC

@vrxj81

vrxj81 commented May 6, 2026

Copy link
Copy Markdown
Contributor Author

Manual test steps

  • created Nest app using nest new nest-test
  • added Nx using nx init
  • installed @nx/nest plugin through local path entry in package.json, running npm install and adding plugin config to nx.json ( { plugins: [ "@nx/nest/plugin"} )
  • removed default nest NPM build target from package.json
  • ran nx show projects
  • ran nx show project nest-test
  • ran nx build nest-test twice (target and cache test)
  • ran nx serve nest-test

Results

nx show projects

nest-test

nx show project nest-test

image

nx build nest-test (first run)


> nx run nest-test:build

> nest build


———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target build for project nest-test (2s)

nx build nest-test (second run)

> nx run nest-test:build  [local cache]

> nest build


———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target build for project nest-test (79ms)

nx serve nest-test

> nx run nest-test:serve

> nest start --watch

[13:30:59] Starting compilation in watch mode...

[13:30:59] Found 0 errors. Watching for file changes.


[Nest] 71857  - 06/05/2026, 13:31:00     LOG [NestFactory] Starting Nest application...
[Nest] 71857  - 06/05/2026, 13:31:00     LOG [InstanceLoader] AppModule dependencies initialized +5ms
[Nest] 71857  - 06/05/2026, 13:31:00     LOG [RoutesResolver] AppController {/}: +1ms
[Nest] 71857  - 06/05/2026, 13:31:00     LOG [RouterExplorer] Mapped {/, GET} route +1ms
[Nest] 71857  - 06/05/2026, 13:31:00     LOG [NestApplication] Nest application successfully started +1ms

———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target serve for project nest-test

@nx-cloud nx-cloud Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nx Cloud has identified a flaky task in your failed CI:

Since the failure was identified as flaky, the solution is to rerun CI. Because this branch comes from a fork, it is not possible for us to push directly, but you can rerun by pushing an empty commit:

git commit --allow-empty -m "chore: trigger rerun"
git push

Nx Cloud View detailed reasoning in Nx Cloud ↗


🎓 Learn more about Self-Healing CI on nx.dev

@FrozenPandaz

Copy link
Copy Markdown
Contributor

Hi @vrxj81 👋

How is this going? Do you need any help? Is it ready for review?

@vrxj81

vrxj81 commented May 20, 2026

Copy link
Copy Markdown
Contributor Author

Hi @vrxj81 👋

How is this going? Do you need any help? Is it ready for review?

hi @FrozenPandaz,
It's like you read my mind.
Any pointers would be helpful.
The code is ready for review, but the CI checks main-linux fail and no clue what to do about it.

@FrozenPandaz

Copy link
Copy Markdown
Contributor

The failures seem unrelated. Please try rebasing.

@vrxj81 vrxj81 force-pushed the feat/nest-plugin-entrypoint branch from 899714b to 3053edd Compare June 5, 2026 08:00
@vrxj81

vrxj81 commented Jun 5, 2026

Copy link
Copy Markdown
Contributor Author

The failures seem unrelated. Please try rebasing.

rebased

@vrxj81 vrxj81 force-pushed the feat/nest-plugin-entrypoint branch from 3053edd to 12e13f5 Compare June 7, 2026 10:52
@vrxj81 vrxj81 force-pushed the feat/nest-plugin-entrypoint branch from 12e13f5 to a21b384 Compare June 7, 2026 11:00
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.

2 participants