If a project has nested projects that contain node_modules folders that get processed by ngcc, it can be confusing when the ngcc version changes since the error message is very generic: ``` The ngcc compiler has changed since the last ngcc build. Please completely remove `node_modules` and try again. ``` This commit augments the error message with the path of the entry-point that failed so that it is more obvious which node_modules folder to remove. BREAKING CHANGE: This commit removes the public export of `hasBeenProcessed()`. This was exported to be availble to the CLI integration but was never used. The change to the function signature is a breaking change in itself so we remove the function altogether to simplify and lower the public API surface going forward. PR Close #32396
		
			
				
	
	
		
			21 lines
		
	
	
		
			750 B
		
	
	
	
		
			TypeScript
		
	
	
	
	
	
			
		
		
	
	
			21 lines
		
	
	
		
			750 B
		
	
	
	
		
			TypeScript
		
	
	
	
	
	
| /**
 | |
|  * @license
 | |
|  * Copyright Google Inc. All Rights Reserved.
 | |
|  *
 | |
|  * Use of this source code is governed by an MIT-style license that can be
 | |
|  * found in the LICENSE file at https://angular.io/license
 | |
|  */
 | |
| import {CachedFileSystem, NodeJSFileSystem, setFileSystem} from '../src/ngtsc/file_system';
 | |
| 
 | |
| import {mainNgcc} from './src/main';
 | |
| export {ConsoleLogger, LogLevel} from './src/logging/console_logger';
 | |
| export {Logger} from './src/logging/logger';
 | |
| export {NgccOptions} from './src/main';
 | |
| export {PathMappings} from './src/utils';
 | |
| 
 | |
| export function process(...args: Parameters<typeof mainNgcc>) {
 | |
|   // Recreate the file system on each call to reset the cache
 | |
|   setFileSystem(new CachedFileSystem(new NodeJSFileSystem()));
 | |
|   return mainNgcc(...args);
 | |
| }
 |