From 37b9f06f1e3255e958e99d047ca7648e5beebd0e Mon Sep 17 00:00:00 2001 From: WilliamKoza Date: Sat, 9 Mar 2019 12:19:53 +0100 Subject: [PATCH] docs: change the file name of the public API according with Angular CLI (#29200) PR Close #29200 --- aio/content/guide/creating-libraries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/creating-libraries.md b/aio/content/guide/creating-libraries.md index 5b54d3e8a8..9716a4b92e 100644 --- a/aio/content/guide/creating-libraries.md +++ b/aio/content/guide/creating-libraries.md @@ -42,7 +42,7 @@ This builder, among other things, ensures that the library is always built with To make library code reusable you must define a public API for it. This "user layer" defines what is available to consumers of your library. A user of your library should be able to access public functionality (such as NgModules, service providers and general utility functions) through a single import path. -The public API for your library is maintained in the `index.ts` file of your library folder. +The public API for your library is maintained in the `public-api.ts` file in your library folder. Anything exported from this file is made public when your library is imported into an application. Use an NgModule to expose services and components.