whitespace

Author: filipesilva

public/docs/ts/latest/cookbook/third-party-lib.jade

@@ -345,12 +345,14 @@ code-example(language="json").
 :marked
   ## Appendix: Supporting AOT
 
-  AOT plays an important role in optimizing Angular applications. It's therefore important that third party libraries be published in a format compatible with AOT compilation. Otherwise it will not be possible to include the library in an AOT compiled application.
+  AOT plays an important role in optimizing Angular applications. 
+  It's therefore important that third party libraries be published in a format compatible with AOT
+  compilation.
+  Otherwise it will not be possible to include the library in an AOT compiled application.
 
   Only code written in TypeScript can be AOT compiled.
 
   Before publishing the library must first be compiled using the `ngc` compiler. 
-  
   `ngc` extends the `tsc` compiler by adding extensions to support AOT compilation in addition to regular TypeScript compilation.   
 
   AOT compilation outputs three files that must be included in order to be compatible with AOT.
@@ -361,27 +363,38 @@ code-example(language="json").
 
   *Typings files*
 
-  JavaScript has no way of representing typings. In order to preserve the original typings, `ngc` will generate `.d.ts` typings files.
+  JavaScript has no way of representing typings. In order to preserve the original typings, `ngc`
+  will generate `.d.ts` typings files.
 
   *Meta Data JSON files*
 
-  `ngc` outputs a metadata.json file for every `Component` and `NgModule`. These meta data files represent the information in the original `NgModule` and `Component` decorators.   
+  `ngc` outputs a metadata.json file for every `Component` and `NgModule`.
+  These meta data files represent the information in the original `NgModule` and `Component`
+  decorators.   
 
-  The meta data may reference external templates or css files. These external files must be included with the library.
+  The meta data may reference external templates or css files.
+  These external files must be included with the library.
 
   ### NgFactories
 
-  `ngc` generates a series of files with an `.ngfactory` suffix as well. These files represent the AOT compiled source, but should not be included with the published library.
+  `ngc` generates a series of files with an `.ngfactory` suffix as well.
+  These files represent the AOT compiled source, but should not be included with the published library.
 
-  Instead the `ngc` compiler in the consuming application will generate `.ngfactory` files based on the JavaScript, Typings and meta data shipped with the library. 
+  Instead the `ngc` compiler in the consuming application will generate `.ngfactory` files based
+   on the JavaScript, Typings and meta data shipped with the library. 
 
   ### Why not publish TypeScript?
 
-  Why not ship TypeScript source instead? After all the library will be part of another TypeScript compilation step when the library is imported by the consuming application? 
+  Why not ship TypeScript source instead? 
+  After all the library will be part of another TypeScript compilation step when the library is
+  imported by the consuming application? 
 
-  Generally it's discouraged to ship TypeScript with third party libraries. It would require the consumer to replicate the complete build environment of the library. Not only typings, but potentially a specific version of `ngc` as well.
+  Generally it's discouraged to ship TypeScript with third party libraries. 
+  It would require the consumer to replicate the complete build environment of the library. 
+  Not only typings, but potentially a specific version of `ngc` as well.
 
-  Publishing plain JavaScript with typings and meta data allows the consuming application to remain agnostic of the library's build environment.
+  Publishing plain JavaScript with typings and meta data allows the consuming application to 
+  remain agnostic of the library's build environment.
 
 
 .l-main-section