angular-library-starter
Build an Angular library compatible with AoT compilation & Tree shaking.
This starter allows you to create a library for Angular 4+ apps written in TypeScript, ES6 or ES5.
The project is based on the official Angular packages.
Get the Changelog.
Contents
1 Project structure
- Library:
- src folder for the classes
- public_api.ts entry point for all public APIs of the package
- package.json npm options
- rollup.config.js Rollup configuration for building the bundles
- tsconfig-build.json ngc compiler options for AoT compilation
- build.js building process using ShellJS
- Testing:
- tests folder for unit & integration tests
- karma.conf.js Karma configuration that uses webpack to build the tests
- spec.bundle.js defines the files used by webpack
- Extra:
- tslint.json TypeScript linter rules with Codelyzer
- travis.yml Travis CI configuration
2 Customizing
-
Update Node & npm.
-
Rename angular-library-starter
and angularLibraryStarter
everywhere to my-library
and myLibrary
.
-
Update in package.json
file:
and run npm install
.
-
Create your classes in src
folder, and export public classes in my-library.ts
.
-
You can create only one module for the whole library:
I suggest you create different modules for different functions,
so that the user can import only those he needs and optimize Tree shaking of his app.
-
Update in rollup.config.js
file globals
external dependencies with those that actually you use.
-
Create unit & integration tests in tests
folder, or unit tests next to the things they test in src
folder, always using .spec.ts
extension.
Karma is configured to use webpack only for *.ts
files: if you need to test different formats, you have to update it.
3 Testing
The following command run unit & integration tests that are in the tests
folder, and unit tests that are in src
folder:
npm test
4 Building
The following command:
npm run build
- starts TSLint with Codelyzer
- starts AoT compilation using ngc compiler
- creates
dist
folder with all the files of distribution
To test locally the npm package:
npm run pack-lib
Then you can install it in an app to test it:
npm install [path]my-library-[version].tgz
5 Publishing
Before publishing the first time:
npm run publish-lib
6 Documentation
To generate the documentation, this starter uses compodoc:
npm run compodoc
npm run compodoc-serve
7 Using the library
Installing
npm install my-library --save
Loading
Using SystemJS configuration
System.config({
map: {
'my-library': 'node_modules/my-library/bundles/my-library.umd.js'
}
});
Angular-CLI
No need to set up anything, just import it in your code.
Rollup or webpack
No need to set up anything, just import it in your code.
Plain JavaScript
Include the umd
bundle in your index.html
:
<script src="node_modules/my-library/bundles/my-library.umd.js"></script>
and use global ng.myLibrary
namespace.
AoT compilation
The library is compatible with AoT compilation.
8 What it is important to know
-
package.json
"main": "./bundles/angular-library-starter.umd.js"
legacy module format"module": "./bundles/angular-library-starter.es5.js"
flat ES module, for using module bundlers such as Rollup or webpack:
package module"es2015": "./bundles/angular-library-starter.js"
ES2015 flat ESM format, experimental ES2015 build"peerDependencies"
the packages and their versions required by the library when it will be installed
-
tsconfig.json
file used by TypeScript compiler
- Compiler options:
"strict": true
enables TypeScript strict
master option
-
tsconfig-build.json
file used by ngc compiler
-
rollup.config.js
file used by Rollup
format: 'umd'
the Universal Module Definition pattern is used by Angular for its bundlesmoduleName: 'ng.angularLibraryStarter'
defines the global namespace used by JavaScript appsexternal
& globals
declare the external packages
-
Server-side prerendering
If you want the library will be compatible with server-side prerendering:
window
, document
, navigator
and other browser types do not exist on the server- don't manipulate the nativeElement directly
License
MIT