It failed when building a next application with config `output:standalone`. #27724

ibufu · 2024-09-01T04:26:31Z

Current Behavior

After integrating to an existed pnpm monorepo, it failed when building a next application with config output:standalone.

Expected Behavior

nx build next-app --verbose

Error: File exists (os error 17)
    at /nx-next-standalone/node_modules/.pnpm/[email protected]/node_modules/nx/src/tasks-runner/cache.js:145:17

GitHub Repo

https://github.com/ibufu/nx-next-standalone

Steps to Reproduce

Clone the repo.
pnpm i
nx build next-app

Nx Report

Node           : 18.20.4
OS             : darwin-arm64
Native Target  : aarch64-macos
pnpm           : 9.9.0

nx (global)  : 19.6.4
nx           : 19.6.4
@nx/eslint   : 19.6.4
@nx/next     : 19.6.4
---------------------------------------
Registered Plugins:
@nx/eslint/plugin
@nx/next/plugin

Failure Logs

Error: File exists (os error 17)
    at /nx-next-standalone/node_modules/.pnpm/[email protected]/node_modules/nx/src/tasks-runner/cache.js:145:17

Package Manager Version

[email protected]

Operating System

macOS
Linux
Windows
Other (Please specify)

Additional Information

No response

The text was updated successfully, but these errors were encountered:

jackhefoong · 2024-11-06T03:22:39Z

Same here

malfianrasyidin · 2024-11-08T09:22:30Z

The issue persists in the latest Nx version (v20.0.11).
Is there any additional action planned to address this?
@jaysoo @ndcunningham

Thanks!

Error: File exists (os error 17)
    at /node_modules/.pnpm/[email protected]/node_modules/nx/src/tasks-runner/cache.js:317:17

ibufu · 2024-11-08T09:25:19Z

Just delete the scripts in package.json and only keep scripts in project.json

…

On Fri, 8 Nov 2024 at 1:22 PM Muhammad Alfian Rasyidin < ***@***.***> wrote: The issue persists in the latest Nx version (v20.0.11). Is there any additional action planned to address this? @jaysoo <https://github.com/jaysoo> @ndcunningham <https://github.com/ndcunningham> Thanks! Error: File exists (os error 17) at ***@***.***/node_modules/nx/src/tasks-runner/cache.js:317:17 — Reply to this email directly, view it on GitHub <#27724 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC5TWOAZONARH6NVIGBKFGTZ7R7G3AVCNFSM6AAAAABNOPB2H6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUGIYTIMBWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

jackhefoong · 2024-11-08T10:07:41Z

Big help, thanks! @ibufu

counterbeing · 2024-11-08T13:24:16Z

I'm getting the same error.

I'm trying to understand how not using package.json scripts would help? I'm also trying to understand how to update my project.json to actually build correctly.I went with a package.json script for this particular library because it has a couple of steps:

    "bundle": "tsx ./src/bundle.ts",
    "build": "rm -rf ./dist && tsc -p tsconfig.lib.json && pnpm run bundle"
  }

How would i convert that into a project.json syntax, and how would that fix the problem? Or would it?

ibufu · 2024-11-08T13:36:17Z

The root cause is that nx run the build script twice. You can use nx show to figure out it.

counterbeing · 2024-11-08T14:02:57Z

I've moved to this structure in my project.json for this package:

{
  "name": "workflow-bundler",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "sourceRoot": "packages/workflow-bundler/src",
  "projectType": "library",
  "tags": [],
  "targets": {
    "build": {
      "executor": "nx:run-commands",
      "options": {
        "command": "say 'hello';rm -rf ./dist && tsc -p tsconfig.lib.json && tsx ./src/bundle.ts"
      }
    }
  }
}

That say 'hello' is just there so i can hear if it happens to run twice. It's now only running once. I've entirely removed the scripts section from my package.json. However i'm still getting:

    at /Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:84:24
    at _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:397:26)
    at _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:406:26)
    at async _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:406:20)
    at async _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:406:20)
    at async _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:406:20)
    at async _try (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/cache.js:406:20)
    at async Promise.all (index 0)
    at async TaskOrchestrator.postRunSteps (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/task-orchestrator.js:345:13)
    at async TaskOrchestrator.applyFromCacheOrRunTask (/Users/cory.logan/Code/my-project/node_modules/.pnpm/[email protected]_@[email protected]_@[email protected]_@[email protected]__@[email protected]_t_rpge6wb46b7rpyw5yhycwpxahy/node_modules/nx/src/tasks-runner/task-orchestrator.js:295:9)

CristianHG2 · 2025-01-10T04:18:25Z

I'm also experiencing this issue. On my end, there seems to be some conflict with the cache entries for Nx. It seems it is trying to write to the cache, but the key already exists, which causes this issue.

Running the command with --skipNxCache worked for me.

caioquirino · 2025-04-03T17:49:48Z

For my setup, the issue was also gone after adding --skipNxCache (which is not the ideal solution). Tested with the latest NX version: 20.7.1

OrenSayag · 2025-04-27T07:42:03Z

--skipNxCache worked around the issue for me too

drewandre · 2025-05-06T15:43:27Z

This is still broken in the latest NV v21.0.0. It's unfortunate because we have to disable standalone output when running outside of CI, which produces a different build, so it's difficult to run our true production compiled next.js app locally.

Steps to reproduce below:

pnpx create-nx-workspace nx-21 using [email protected] with the following options:

"React" for stack
"Next.js" for framework
App Router: yes
src/ directory: yes
Unit test runner: Jest
E2E test runner: Playwright
Stylesheet: tailwind
Eslint: yes
Prettier: yes

Add output: "standalone" to next.config.js
Run inferred next.js build command - see output error

Besides react and next.js, I don't think the choices above make a difference - I haven't tried with a different test runner or style system for example. But just a basic [email protected] standalone next.js build fails pretty easily.

A lot of next.js builds are dockerized (to avoid high vercel pricing), which is why standalone is so important. Our team isn't completely blocked because we just disable nx caching in our CI pipeline. And yes, --skipNxCache does fix the issue, but obviously not a long term solution.

ianldgs for visibility, since we had a brief discussion on #30733 earlier.

nx report

Node : 20.19.0 OS : darwin-arm64 Native Target : aarch64-macos pnpm : 10.8.0

nx : 21.0.0
@nx/js : 21.0.0
@nx/jest : 21.0.0
@nx/eslint : 21.0.0
@nx/workspace : 21.0.0
@nx/devkit : 21.0.0
@nx/eslint-plugin : 21.0.0
@nx/module-federation : 21.0.0
@nx/next : 21.0.0
@nx/playwright : 21.0.0
@nx/react : 21.0.0
@nx/web : 21.0.0
@nx/webpack : 21.0.0
typescript : 5.7.3

Registered Plugins:
@nx/js/typescript
@nx/next/plugin
@nx/playwright/plugin
@nx/eslint/plugin
@nx/jest/plugin

Cache Usage: 0.00 B / 92.64 GB

ibufu added the type: bug label Sep 1, 2024

jaysoo added the scope: nextjs Issues related to NextJS support for Nx label Sep 25, 2024

jaysoo assigned ndcunningham Sep 25, 2024

drewandre mentioned this issue May 6, 2025

NX No such file or directory (os error 2) - when using the new remote cache from 20.8 #30733

Closed

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

It failed when building a next application with config `output:standalone`. #27724

It failed when building a next application with config `output:standalone`. #27724

ibufu commented Sep 1, 2024

jackhefoong commented Nov 6, 2024

Uh oh!

malfianrasyidin commented Nov 8, 2024

Uh oh!

ibufu commented Nov 8, 2024 via email

Uh oh!

jackhefoong commented Nov 8, 2024

Uh oh!

counterbeing commented Nov 8, 2024 •

edited

Loading

Uh oh!

ibufu commented Nov 8, 2024

Uh oh!

counterbeing commented Nov 8, 2024

Uh oh!

CristianHG2 commented Jan 10, 2025

Uh oh!

caioquirino commented Apr 3, 2025

Uh oh!

OrenSayag commented Apr 27, 2025

Uh oh!

drewandre commented May 6, 2025 •

edited

Loading

nx : 21.0.0
@nx/js : 21.0.0
@nx/jest : 21.0.0
@nx/eslint : 21.0.0
@nx/workspace : 21.0.0
@nx/devkit : 21.0.0
@nx/eslint-plugin : 21.0.0
@nx/module-federation : 21.0.0
@nx/next : 21.0.0
@nx/playwright : 21.0.0
@nx/react : 21.0.0
@nx/web : 21.0.0
@nx/webpack : 21.0.0
typescript : 5.7.3

Registered Plugins:
@nx/js/typescript
@nx/next/plugin
@nx/playwright/plugin
@nx/eslint/plugin
@nx/jest/plugin

Uh oh!

It failed when building a next application with config output:standalone. #27724

It failed when building a next application with config output:standalone. #27724

Comments

ibufu commented Sep 1, 2024

Current Behavior

Expected Behavior

GitHub Repo

Steps to Reproduce

Nx Report

Failure Logs

Package Manager Version

Operating System

Additional Information

jackhefoong commented Nov 6, 2024

Uh oh!

malfianrasyidin commented Nov 8, 2024

Uh oh!

ibufu commented Nov 8, 2024 via email

Uh oh!

jackhefoong commented Nov 8, 2024

Uh oh!

counterbeing commented Nov 8, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ibufu commented Nov 8, 2024

Uh oh!

counterbeing commented Nov 8, 2024

Uh oh!

CristianHG2 commented Jan 10, 2025

Uh oh!

caioquirino commented Apr 3, 2025

Uh oh!

OrenSayag commented Apr 27, 2025

Uh oh!

drewandre commented May 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

nx : 21.0.0 @nx/js : 21.0.0 @nx/jest : 21.0.0 @nx/eslint : 21.0.0 @nx/workspace : 21.0.0 @nx/devkit : 21.0.0 @nx/eslint-plugin : 21.0.0 @nx/module-federation : 21.0.0 @nx/next : 21.0.0 @nx/playwright : 21.0.0 @nx/react : 21.0.0 @nx/web : 21.0.0 @nx/webpack : 21.0.0 typescript : 5.7.3

Registered Plugins: @nx/js/typescript @nx/next/plugin @nx/playwright/plugin @nx/eslint/plugin @nx/jest/plugin

Uh oh!

It failed when building a next application with config `output:standalone`. #27724

It failed when building a next application with config `output:standalone`. #27724

counterbeing commented Nov 8, 2024 •

edited

Loading

drewandre commented May 6, 2025 •

edited

Loading

nx : 21.0.0
@nx/js : 21.0.0
@nx/jest : 21.0.0
@nx/eslint : 21.0.0
@nx/workspace : 21.0.0
@nx/devkit : 21.0.0
@nx/eslint-plugin : 21.0.0
@nx/module-federation : 21.0.0
@nx/next : 21.0.0
@nx/playwright : 21.0.0
@nx/react : 21.0.0
@nx/web : 21.0.0
@nx/webpack : 21.0.0
typescript : 5.7.3

Registered Plugins:
@nx/js/typescript
@nx/next/plugin
@nx/playwright/plugin
@nx/eslint/plugin
@nx/jest/plugin