feat(nextjs): allow withNx to be used with other executors such as run-commands

[jaysoo]

This PR allows withNx plugin to be used without @nx/next:build or @nx/next:server executors. As long as the command runs through Nx we can read the run information (e.g. project node, options, config) from the project graph.

Why?

There are legit cases where users may not use @nx/next:build or other expected executors.

1. They wrap out @nx/next:build into their own custom plugin, say @acme/next:build.
2. They use run-commands to execute npx next build directly.

After some thought, they only special case is that buildTarget or devServerTarget may be present, which requires additional reading of those target configurations. These special cases could be @nx/next:server that specify buildTarget, which defines the outputPath for example. Or when Cypress defines a devServerTarget, which then defines a buildTarget, so we need to follow that target chain fully.

In all other cases, we can safely fallback to the default behavior, which is to return the configuration for the current target. This could be either @nx/next:build, run-commands, or a custom executor.

Current Behavior

Using run-commands or command breaks with withNx.

Expected Behavior

Using run-commands or command does not break with withNx.

Related Issue(s)

Fixes #16064, #16277

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 27, 2023 1:36pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b955e21. 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 target

• nx affected -t e2e-macos --parallel=1 --base=fdf755584fb74aff8e0e4c598e0ae3600ca2f6bf --head=b955e213b3a3074567eb5dd6767a222d7fb43dd8

---

Sent with 💌 from NxCloud.

[jaysoo]

We really don't care about exports at this point since it's a deprecated Next.js command.

[ndcunningham]

LGTM

[github-actions]

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.