Skip to content

angular-package/error

Repository files navigation

angular-package

The angular-package supports the development process of angular-based applications in varied ways through the thoughtful, reusable, easy-to-use small pieces of code called packages.

docs.angular-package.dev


Packages

Package Description Status
callback Manages the callback function. npm version
change-detection Improves application performance. npm version
component-loader Handles dynamic loading components. npm version
core Core features. npm version
error Manages an Error. npm version
name The name with prefix and suffix. npm version
preferences Preferences, settings, options, configuration and setup in steps. npm version
prism Prism highlighter module. npm version
property Handles object properties. npm version
range The range between a minimum and maximum. npm version
reactive Automatize the process of creating some rxjs features. npm version
storage The storage of data under allowed names. npm version
tag Any tag with optional attributes. npm version
testing Support for testing other packages. npm version
text Text on the template with replaceable tags. npm version
type Common types, type guards, and type checkers. npm version
ui User interface. In Progress
wrapper Wrap the text with the opening and closing chars. npm version

Click on the package name to visit its GitHub page.


angular-package/error

Manages an Error.

Gitter Discord Twitter

npm version

GitHub issues GitHub forks GitHub stars GitHub license

GitHub sponsors Support me on Patreon


Documentation

For the detailed documentation go to https://error.angular-package.dev


Table of contents


Skeleton

This package was built by the library skeleton which was generated with Angular CLI version 12.2.5.

Copy this package to the packages/error folder of the library skeleton then run the commands below.

Code scaffolding

Run ng generate component component-name --project error to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project storage.

Note: Don't forget to add --project error or else it will be added to the default project in your angular.json file.

Build

Run ng build error to build the package. The build artifacts will be stored in the dist/ directory.

Publishing

After building your library with ng build error, go to the dist folder cd dist/error and run npm publish.

Running unit tests

Install @angular-package/testing with command:

npm i @angular-package/testing --no-save

Run ng test error to execute the unit tests via Karma.


Installation

Install @angular-package/error package with command:

npm i @angular-package/error --save

Changelog

The changelog of this package is based on keep a changelog. To read it, click on the CHANGELOG.md link.

A changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. - keep a changelog


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)