.next dir still in old outputPath when overriding using --outputPath cli flag on next.js build

[dotrakoun-clearstreet]

Current Behavior

have next generated project with project.json

"targets": {
                "build": {
                        "executor": "@nx/next:build",
                        "outputs": ["{options.outputPath}"],
                        "options": {
                                "outputPath": "dist"
                        },
...

run

nx build nextjsproj -c production --outputPath=dist/sub

and you get dist/sub/* files
but no .next/ dir
the .next/ dir is generated in dist/.next

Expected Behavior

dist/sub/*
dist/sub/.next

.next should be colocated with rest of output so you can run npm run start from the dist/sub directory

GitHub Repo

No response

Steps to Reproduce

1. next nextjs project with above project.json config
2. build it with a outputPath path cli flag override

Nx Report

>  NX  Falling back to ts-node for local typescript execution. This may be a little slower.
  - To fix this, ensure @swc-node/register and @swc/core have been installed

 >  NX   Report complete - copy this into the issue template

   Node   : 18.16.0
   OS     : linux-x64
   pnpm   : 8.5.0

   nx                 : 16.4.0
   @nx/js             : 16.4.0
   @nx/jest           : 16.4.0
   @nx/linter         : 16.4.0
   @nx/workspace      : 16.4.0
   @nx/cypress        : 16.4.0
   @nx/devkit         : 16.4.0
   @nx/esbuild        : 16.4.0
   @nx/eslint-plugin  : 16.4.0
   @nx/next           : 16.4.0
   @nx/node           : 16.4.0
   @nx/react          : 16.4.0
   @nx/rollup         : 16.4.0
   @nx/storybook      : 16.4.0
   @nrwl/tao          : 16.4.0
   @nx/web            : 16.4.0
   @nx/webpack        : 16.4.0
   typescript         : 4.9.5
   ---------------------------------------
   Community plugins:
   @trumbitta/nx-plugin-unused-deps : 1.12.1
   ---------------------------------------

Failure Logs

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[github-actions]

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.