feat(nextjs): Add support for create nodes for nextjs

[ndcunningham]

Current Behavior

There is no plugin to run Nextjs projects (a project containing next.config.js)

Expected Behavior

Using this plugin @nx/next/plugin inside a fresh will create targets (build, start & dev) to nx.json.
The user should now be able to run these targets without configuring a project.json.

How to Use

Add this to your nx.json plugins

  "plugins": [
    {
      "plugin": "@nx/next/plugin",
      "options": {
        "buildTargetName": "build", // <--- These names you can changed to your liking
        "startTargetName": "start",
        "devTargetName": "dev",
      }
    }
  ]

For new projects when you create a Nextjs project this will already be set up for you after passing NX_PCV3=true.

NX_PCV3=true nx generate @nx/next:app ${appName} --project-name-and-root-format=as-provided --no-interactive

NB

next export has been deprecated in favor of:

const nextConfig = {
//....... other configs

  output: 'export'
};

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Dec 6, 2023 10:44pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a0b4507. 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 6 targets

• nx affected --target=e2e --base=7ffc3284f604224324a9c7e75a0a44fb8c45587b --head=a0b45070997b4d29d60628c947a9db71f53c8151 --parallel=1
• nx affected --targets=lint,test,build --base=7ffc3284f604224324a9c7e75a0a44fb8c45587b --head=a0b45070997b4d29d60628c947a9db71f53c8151 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=7ffc3284f604224324a9c7e75a0a44fb8c45587b --head=a0b45070997b4d29d60628c947a9db71f53c8151
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=7ffc3284f604224324a9c7e75a0a44fb8c45587b --head=a0b45070997b4d29d60628c947a9db71f53c8151

---

Sent with 💌 from NxCloud.

[ndcunningham]

build only creates production artifacts so this test case was wrong before.

[jaysoo]

Added some comments. I think the rest looks fine.

[jaysoo]

We'll need to check what's still needed from withNx and what features require the full Nx context (task name, graph, etc.). If we can simplify the new setup we should, and leave legacy behavior for existing projects.

[ndcunningham]

We'll need to check what's still needed from withNx and what features require the full Nx context (task name, graph, etc.). If we can simplify the new setup we should, and leave legacy behavior for existing projects.

Updated:

• Now we don't generate .nx-helpers nor next.config.js inside dist
• For those we will need nx context (Docker) will need require @nx/next as a prod dependency

[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.