7186f9c016
To improve cross platform support, all file access (and path manipulation) is now done through a well known interface (`FileSystem`). For testing a number of `MockFileSystem` implementations are provided. These provide an in-memory file-system which emulates operating systems like OS/X, Unix and Windows. The current file system is always available via the static method, `FileSystem.getFileSystem()`. This is also used by a number of static methods on `AbsoluteFsPath` and `PathSegment`, to avoid having to pass `FileSystem` objects around all the time. The result of this is that one must be careful to ensure that the file-system has been initialized before using any of these static methods. To prevent this happening accidentally the current file system always starts out as an instance of `InvalidFileSystem`, which will throw an error if any of its methods are called. You can set the current file-system by calling `FileSystem.setFileSystem()`. During testing you can call the helper function `initMockFileSystem(os)` which takes a string name of the OS to emulate, and will also monkey-patch aspects of the TypeScript library to ensure that TS is also using the current file-system. Finally there is the `NgtscCompilerHost` to be used for any TypeScript compilation, which uses a given file-system. All tests that interact with the file-system should be tested against each of the mock file-systems. A series of helpers have been provided to support such tests: * `runInEachFileSystem()` - wrap your tests in this helper to run all the wrapped tests in each of the mock file-systems. * `addTestFilesToFileSystem()` - use this to add files and their contents to the mock file system for testing. * `loadTestFilesFromDisk()` - use this to load a mirror image of files on disk into the in-memory mock file-system. * `loadFakeCore()` - use this to load a fake version of `@angular/core` into the mock file-system. All ngcc and ngtsc source and tests now use this virtual file-system setup. PR Close #30921
50 lines
1.9 KiB
TypeScript
50 lines
1.9 KiB
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
|
|
*/
|
|
/// <reference types="node" />
|
|
|
|
import * as fs from 'fs';
|
|
import * as path from 'path';
|
|
|
|
/**
|
|
* Gets all built Angular NPM package artifacts by querying the Bazel runfiles.
|
|
* In case there is a runfiles manifest (e.g. on Windows), the packages are resolved
|
|
* through the manifest because the runfiles are not symlinked and cannot be searched
|
|
* within the real filesystem.
|
|
*/
|
|
export function getAngularPackagesFromRunfiles() {
|
|
// Path to the Bazel runfiles manifest if present. This file is present if runfiles are
|
|
// not symlinked into the runfiles directory.
|
|
const runfilesManifestPath = process.env.RUNFILES_MANIFEST_FILE;
|
|
|
|
if (!runfilesManifestPath) {
|
|
const packageRunfilesDir = path.join(process.env.RUNFILES !, 'angular/packages');
|
|
|
|
return fs.readdirSync(packageRunfilesDir)
|
|
.map(name => ({name, pkgPath: path.join(packageRunfilesDir, name, 'npm_package/')}))
|
|
.filter(({pkgPath}) => fs.existsSync(pkgPath));
|
|
}
|
|
|
|
return fs.readFileSync(runfilesManifestPath, 'utf8')
|
|
.split('\n')
|
|
.map(mapping => mapping.split(' '))
|
|
.filter(([runfilePath]) => runfilePath.match(/^angular\/packages\/[\w-]+\/npm_package$/))
|
|
.map(([runfilePath, realPath]) => ({
|
|
name: path.relative('angular/packages', runfilePath).split(path.sep)[0],
|
|
pkgPath: realPath,
|
|
}));
|
|
}
|
|
|
|
/**
|
|
* Resolves a NPM package from the Bazel runfiles. We need to resolve the Bazel tree
|
|
* artifacts using a "resolve file" because the NodeJS module resolution does not allow
|
|
* resolving to directory paths.
|
|
*/
|
|
export function resolveNpmTreeArtifact(manifestPath: string, resolveFile = 'package.json') {
|
|
return path.dirname(require.resolve(path.posix.join(manifestPath, resolveFile)));
|
|
}
|