[error] Error: EISDIR: Angular v17 using esbuild

[DominicWrege]

🐞 Bug report

Command

build

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

16

Description

When opting for the es-build feature over webpack. An exception occurred which does not have any context. This is unacceptable. It should at least print out on which file or directory the error occurred.

I simply change this in my angular.json file.

Fails:

"builder": "@angular-devkit/build-angular:browser-esbuild",

Works:

builder": "@angular-devkit/build-angular:browser",

Minimal Reproduction

ng build --configuration production --verbose

output:

> project@web.management@1.0.7 build
> ng build --configuration production --verbose

⠙ Building...

  polyfills-LZBJRJJE.js  32.7kb

⠇ Building...

  chunk-2FFGP3PS.js  993.4kb
  chunk-RCON6BW6.js  652.2kb
  main-HGXVCJ3H.js    59.1kb
  chunk-6BA7RJO3.js   31.1kb
  chunk-ZZLLJRB6.js   20.3kb
  chunk-2HU5B4AX.js   19.5kb
  chunk-4KKN7QDQ.js   14.4kb
  ...and 9 more output files...

An unhandled exception occurred: EISDIR: illegal operation on a directory, read
See "C:\Users\DOMINI~1\AppData\Local\Temp\ng-mDUayD\angular-errors.log" for further details.

Exception or Error

An unhandled exception occurred: EISDIR: illegal operation on a directory, read
See "C:\Users\DOMINI~1\AppData\Local\Temp\ng-mDUayD\angular-errors.log" for further details.

Content:

[error] Error: EISDIR: illegal operation on a directory, read

Your Environment

Angular CLI: 17.0.7
Node: 20.10.0
Package Manager: npm 10.2.5
OS: win32 x64

Angular: 17.0.7
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1700.7
@angular-devkit/build-angular   17.0.7
@angular-devkit/core            17.0.7
@angular-devkit/schematics      17.0.7
@angular/cdk                    17.0.4
@schematics/angular             17.0.7
rxjs                            7.8.1
typescript                      5.2.2
zone.js                         0.14.2

Anything else relevant?

No response

[alan-agius4]

Can you please provide the full contents of the error log including the stacktraces and also the build section of yopur angular.json configuration?

[DominicWrege]

angular.json

{
    "build": {
        "builder": "@angular-devkit/build-angular:browser-esbuild",
        "options": {
            "outputPath": "./dist/frontend",
            "index": "./src/index.html",
            "main": "./src/main.ts",
            "polyfills": "zone.js",
            "tsConfig": "tsconfig.app.json",
            "assets": ["./src/favicon.ico", "./src/assets"],
            "styles": [
                "./src/styles.css",
                "node_modules/@myorg/ngx-ui/style.css",
                "node_modules/@ag-grid-community/styles/ag-grid.css",
                "node_modules/@ag-grid-community/styles/ag-theme-material.css",
                "node_modules/ngx-toastr/toastr.css",
                "node_modules/ngx-spinner/animations/ball-clip-rotate.css"
            ],
            "allowedCommonJsDependencies": ["flat"],
            "scripts": []
        },
        "configurations": {
            "production": {
                "index": "",
                "sourceMap": false,
                "optimization": true,
                "aot": true,
                "budgets": [
                    {
                        "type": "initial",
                        "maximumWarning": "1mb",
                        "maximumError": "1.35mb"
                    },
                    {
                        "type": "anyComponentStyle",
                        "maximumWarning": "2kb",
                        "maximumError": "4kb"
                    }
                ],
                "fileReplacements": [
                    {
                        "replace": "./src/environments/environment.development.ts",
                        "with": "./src/environments/environment.ts"
                    }
                ],
                "outputHashing": "all"
            },
            "development": {
                "buildOptimizer": false,
                "optimization": false,
                "extractLicenses": false,
                "sourceMap": true,
                "namedChunks": true
            }
        },
        "defaultConfiguration": "production"
    }
}

[DominicWrege]

Can you please provide the full contents of the error log including the stacktraces and also the build section of yopur angular.json configuration?

I already provided the full error log?!

$ cat C:\Users\DOMINI~1\AppData\Local\Temp\ng-mDUayD\angular-errors.log

[error] Error: EISDIR: illegal operation on a directory, read

Like a wrote, a better error message would help both of us.
With the current webpack based builder, this project builds fine.
With a fresh project, the new esbuild option works.

[alan-agius4]

it is strange that there is no stack trace. Do you have any sort of non alphanumeric characters in the path or symlinks? Unfortunately, I was not able to reproduce with the steps and information provided above.

[DominicWrege]

Do you have any sort of non alphanumeric characters in the path or symlinks?

no

Do you have another idea why there is no stack trace?

[alan-agius4]

So the reason why there is no stacktrace is a known Node.js issue nodejs/node#30944

What you can try is:

npm install trace
node --stack_trace_limit=100 -r trace ./node_modules/@angular/cli/lib/init.js build

[DominicWrege]

Now i have this stack trace:

[error] Error: EISDIR: illegal operation on a directory, read
    at emitInitNative (node:internal/async_hooks:202:43)
    at emitInitNative (node:internal/async_hooks:202:43)
    at emitInitScript (node:internal/async_hooks:505:3)
    at promiseInitHook (node:internal/async_hooks:324:3)
    at promiseInitHookWithDestroyTracking (node:internal/async_hooks:328:3)
    at runCommand (C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\src\command-builder\command-runner.js:26:26)
    at default_1 (C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\lib\cli\index.js:70:54)
    at C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\lib\init.js:140:25
    at emitInitNative (node:internal/async_hooks:202:43)
    at emitInitScript (node:internal/async_hooks:505:3)
    at promiseInitHook (node:internal/async_hooks:324:3)
    at promiseInitHookWithDestroyTracking (node:internal/async_hooks:328:3)
    at Promise.then (<anonymous>)
    at Object.<anonymous> (C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\lib\init.js:140:6)
    at emitInitNative (node:internal/async_hooks:202:43)
    at emitInitScript (node:internal/async_hooks:505:3)
    at promiseInitHook (node:internal/async_hooks:324:3)
    at promiseInitHookWithDestroyTracking (node:internal/async_hooks:328:3)
    at C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\lib\init.js:50:2
    at Object.<anonymous> (C:\Users\Dominic Wrege\source\org\Identity\projectxy\node_modules\@angular\cli\lib\init.js:139:3)
    at Module._compile (node:internal/modules/cjs/loader:1376:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
    at Module.load (node:internal/modules/cjs/loader:1207:32)
    at Module._load (node:internal/modules/cjs/loader:1023:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49

[alan-agius4]

Does the error happen when running ng build --configuration=production --no-optimization?

[DominicWrege]

Running:

 node --stack_trace_limit=100 -r trace ./node_modules/@angular/cli/lib/init.js build --configuration=production --no-optimization

Yes, the error also happens.
The stack trace is identical.

[DominicWrege]

Looking at the stack trace, this looks kind of odd:

at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)

[alan-agius4]

That's just node.js internal modules. Unfortunately however the stacktrace is not helpful as it doesn't indicate the origin.

I am suspecting it's something related to the assets, can you try to remove the assets array?