1.0.1 • Published 5 years ago

@angular-package/core v1.0.1

Weekly downloads
9
License
MIT
Repository
github
Last release
5 years ago

core

Some features used in other angular-package libraries.

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

PackageDescriptionStatusReadme
component-loaderFeatures to make handle dynamic component easier.ReadyReadme
interfaceCommon angular-package typescript interfaces.Ready-
storeStores target setters/getters and cycle-hooks.Ready-
typeCommon angular-package typesscript types.Ready-

GIT

Commit

Versioning

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)

1.0.1

5 years ago

1.0.0

5 years ago

0.1.3

5 years ago

0.1.2

5 years ago