core

Some features used in other angular-package libraries.

``typescript
import '@angular-package/core';
``

Pros(+):
* Treeshake bundle with Rollup - module bundler for JavaScript.
AOT (Ahead Of Time Compilation) package: faster rendering, fewer asynchronous requests, smaller Angular framework download size, detect template errors earlier, better security*.
* MIT License: it can be used commercially.
* Features to make handle dynamic component easier.
* Store setters/getters and cycle hooks.

Cons(-):
* Not everything is tested with jasmine.

----

* Available packages
* Git
* Commit
* Versioning
* License

----

Available packages

| Package | Description | Status | Readme |
|---------------------------|---------------------------------------------------------|------------|-------------|
| component-loader | Features to make handle dynamic component easier. | Ready | [Readme][0] |
| interface | Common angular-package typescript interfaces. | Ready | - |
| store | Stores target setters/getters and cycle-hooks. | Ready | - |
| type | Common angular-package typesscript types. | Ready | - |

[0]: https://github.com/angular-package/angular-package/tree/master/packages/core/packages/component-loader#readme
[1]: https://github.com/angular-package/angular-package/tree/master/packages/core/packages/store#readme

GIT

$3

- AngularJS Git Commit Message Conventions
- Karma Git Commit Msg

$3

Semantic Versioning 2.0.0

Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

FAQ
How should I deal with revisions in the 0.y.z initial development phase?
>The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

>If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

License

MIT © angular-package (license)