angular-docs-cn/packages/compiler-cli/src/ngtsc/routing/index.ts

/**
 * @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" />

export {LazyRoute, NgModuleRouteAnalyzer} from './src/analyzer';
export {entryPointKeyFor} from './src/route';
feat(ivy): implement ngtsc's route analysis (#27697) This commit introduces the NgModuleRouteAnalyzer & friends, which given metadata about the NgModules in a program can extract the list of lazy routes in the same format that the ngtools API uses. PR Close #27697 2018-11-16 17:52:55 +01:00			`/**`
			`* @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" />`

			`export {LazyRoute, NgModuleRouteAnalyzer} from './src/analyzer';`
fix(ivy): support listing lazy route for project-root-relative entry point in `ngtsc` (#28542) I don't know of any use of this API with a project-root-relative path (i.e. the cli will always call it with an absolute path), but keeping the API backwards compatible just in case. PR Close #28542 2019-02-07 19:03:13 +02:00			`export {entryPointKeyFor} from './src/route';`