Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Regression in 11.1.2: ENOENT: no such file or directory
See original GitHub issueType of Issue
[x] Bug Report
[ ] Feature Request
Description
A bug: please describe the error that you encountered
After upgrade to ng-packagr | 11.0.3 -> 11.1.2 I have problem with build
https://github.com/Angular-RU/angular-ru-sdk/pull/361/checks?check_run_id=1736875741
@angular-ru/common: $ ng build library && cp README.md dist/library
@angular-ru/common: Building Angular Package
@angular-ru/common: ******************************************************************************
@angular-ru/common: It is not recommended to publish Ivy libraries to NPM repositories.
@angular-ru/common: Read more here: https://v9.angular.io/guide/ivy#maintaining-library-compatibility
@angular-ru/common: ******************************************************************************
@angular-ru/common: ------------------------------------------------------------------------------
@angular-ru/common: Building entry point '@angular-ru/common'
@angular-ru/common: ------------------------------------------------------------------------------
@angular-ru/common: - Compiling TypeScript sources through NGC
@angular-ru/common: Error: ENOENT: no such file or directory, open '/home/runner/work/angular-ru-sdk/angular-ru-sdk/packages/common/src/**/*.ts'
@angular-ru/common: at Object.openSync (fs.js:476:3)
@angular-ru/common: at Object.readFileSync (fs.js:377:35)
@angular-ru/common: at NodeJSFileSystem.NodeJSReadonlyFileSystem.readFile (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/src/ngtsc/file_system/src/node_js_file_system.js:98:23)
@angular-ru/common: at EsmDependencyHost.DependencyHostBase.recursivelyCollectDependencies (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/dependencies/dependency_host.js:81:40)
@angular-ru/common: at EsmDependencyHost.DependencyHostBase.processFile (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/dependencies/dependency_host.js:136:22)
@angular-ru/common: at EsmDependencyHost.DependencyHostBase.collectDependenciesInFiles (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/dependencies/dependency_host.js:56:26)
@angular-ru/common: at ProgramBasedEntryPointFinder.getInitialEntryPointPaths (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/entry_point_finder/program_based_entry_point_finder.js:49:18)
@angular-ru/common: at ProgramBasedEntryPointFinder.TracingEntryPointFinder.findEntryPoints (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/entry_point_finder/tracing_entry_point_finder.js:45:41)
@angular-ru/common: at /home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/execution/analyze_entry_points.js:28:41
@angular-ru/common: at SingleProcessExecutorAsync.SingleProcessorExecutorBase.doExecute (/home/runner/work/angular-ru-sdk/angular-ru-sdk/node_modules/@angular/compiler-cli/ngcc/src/execution/single_process_executor.js:28:29)
@angular-ru/common: ✖ Compiling TypeScript sources through NGC
@angular-ru/common: ERROR: NGCC failed.
@angular-ru/common: An unhandled exception occurred: NGCC failed.
@angular-ru/common: See "/tmp/ng-pAyPtN/angular-errors.log" for further details.
@angular-ru/common: error Command failed with exit code 127.
@angular-ru/common: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
lerna ERR! yarn run build:lib exited 127 in '@angular-ru/common'
lerna WARN complete Waiting for 1 child process to exit. CTRL-C to exit immediately.
error Command failed with exit code 127.
How To Reproduce
A bug: please include instructions how to reproduce. Issues without reproduction are likely to receive no feedback.
- Git clone https://github.com/Angular-RU/angular-ru-sdk/
- Install ng-packagr 11.1.2
- run
yarn build:lib
Expected Behaviour
A bug: please describe what behaviour or result you expected
Working without regression
Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr: 11.1.2
@angular/*: last
typescript: last
rxjs: last
node: last
yarn: 1.2
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
yarn install fails with `ENOENT: no such file or directory ...
Running yarn install as part of a build step for a Docker image based on node:7 fails on Travis CI with ENOTEMPTY, EEXISTS...
Read more >How to resolve Nodejs: Error: ENOENT: no such file or directory
Your app is expecting to find a file at /home/embah/node/nodeapp/config/config.json but that file does not exist (which is what ENOENT ...
Read more >ENOENT No Such File or Directory Open - YouTube
In This Video We Will See How to Fix npm ERR Code ENOENT npm ERR syscall Open Error or ENOENT No Such File...
Read more >23471 – [2.31.1, regression] /usr/bin/objcopy - sourceware.org
This shows the regression: Version 2.31.1-2 in Debian: ... F_OK) = -1 ENOENT (No such file or directory) access("/etc/ld.so.preload", ...
Read more >ENOENT: no such file or directory when deployed to Vercel
This was happening on my homepage and while most of the site is statically generated, that page isn't. I use getServerSideProps to load...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@splincode, yeah.
@alan-agius4 thanks, great find. That does indeed look like the cause here.