@angular@8.2.0-next.0: ERROR in ENOTDIR: not a directory, scandir *****/index.ts

🐞 bug report

Affected Package

Angular 8.2.0-next.0

I wasn’t able to compile an Ivy project using @angular@8.2.0-next.0 with Ivy enabled. It compiles using @angular 8.1.0

Is this a regression?

Yes, the previous version in which this bug was not present was: Angular 8.1.0-next.3

Description

I’m trying to compile an existing project (@nrwl recommended structure) using Ivy

🔬 Minimal Reproduction

🔥 Exception or Error

ERROR in ENOTDIR: not a directory, scandir 'E:/Users/Juliano/Documents/Projetos/sa/sa-ui/saWorkspace/libs/issue-tracker/data-access/model/src/index.ts'

----------------------------------------------

10 silly lifecycle sa@0.0.0~build-pre: Args: [
10 silly lifecycle   '/d /s /c',
10 silly lifecycle   'ng build --configuration=preproduction --base-href /tutoria/'
10 silly lifecycle ]
11 silly lifecycle sa@0.0.0~build-pre: Returned: code: 1  signal: null
12 info lifecycle sa@0.0.0~build-pre: Failed to exec build-pre script
13 verbose stack Error: sa@0.0.0 build-pre: `ng build --configuration=preproduction --base-href /tutoria/`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\Juliano\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:200:13)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\Juliano\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:200:13)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid sa@0.0.0
15 verbose cwd E:\Users\Juliano\Documents\Projetos\sa\sa-ui\saWorkspace
16 verbose Windows_NT 10.0.17134
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Juliano\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "build-pre"
18 verbose node v12.3.1
19 verbose npm  v6.9.2
20 error code ELIFECYCLE
21 error errno 1
22 error sa@0.0.0 build-pre: `ng build --configuration=preproduction --base-href /tutoria/`
22 error Exit status 1
23 error Failed at the sa@0.0.0 build-pre script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[petebacondarwin]

ng2-file-upload is on our radar. See https://docs.google.com/spreadsheets/d/1TEawfLbWQjqTDst2Jrm2KF6udMVMjuKiz8LG4NPD7WQ/edit#gid=0

[petebacondarwin]

Ahah! But running it targeted on the linqts does fail:

yarn ivy-ngcc -l debug -t linqts

leads to

Error: ENOENT: no such file or directory, lstat '...temp/node_modules/linqts/index.ts'
    at Object.lstatSync (fs.js:840:3)
    at NodeJSFileSystem.lstat (...temp/node_modules/@angular/compiler-cli/src/ngtsc/file_system/src/node_js_file_system.js:38:72)
    at CachedFileSystem.lstat (...temp/node_modules/@angular/compiler-cli/src/ngtsc/file_system/src/cached_file_system.js:87:38)
    at CachedFileSystem.readFile (...temp/node_modules/@angular/compiler-cli/src/ngtsc/file_system/src/cached_file_system.js:35:30)
    at EsmDependencyHost.recursivelyFindDependencies (...temp/node_modules/@angular/compiler-cli/ngcc/src/dependencies/esm_dependency_host.js:59:40)
    at EsmDependencyHost.findDependencies (...temp/node_modules/@angular/compiler-cli/ngcc/src/dependencies/esm_dependency_host.js:41:18)
    at DependencyResolver.getEntryPointDependencies (...temp/node_modules/@angular/compiler-cli/ngcc/src/dependencies/dependency_resolver.js:66:25)
    at TargetedEntryPointFinder.processNextPath (...temp/node_modules/@angular/compiler-cli/ngcc/src/entry_point_finder/targeted_entry_point_finder.js:57:42)
    at TargetedEntryPointFinder.findEntryPoints (...temp/node_modules/@angular/compiler-cli/ngcc/src/entry_point_finder/targeted_entry_point_finder.js:46:22)
    at getTargetedEntryPoints (...temp/node_modules/@angular/compiler-cli/ngcc/src/main.js:141:37)

which is what running via the CLI will do.

This will be fixed by https://github.com/angular/angular/pull/31509