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.
| 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.
Text on the template with replaceable tags.
GitHub issues GitHub forks GitHub stars GitHub license
GitHub sponsors Support me on Patreon
For the detailed documentation go to https://docs.angular-package.dev/v/text-v1.x/
This package was generated by the library skeleton with Angular CLI version 13.0.0.
Copy this package to the packages/text folder of the library skeleton then run the commands below.
Run ng generate component component-name --project text to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project preferences.
Note: Don't forget to add
--project textor else it will be added to the default project in yourangular.jsonfile.
Run ng build text to build the package. The build artifacts will be stored in the dist/ directory.
After building your library with ng build text, go to the dist folder cd dist/text and run npm publish.
Install @angular-package/text with command:
npm i @angular-package/testing --no-save
Run ng test text to execute the unit tests via Karma.
To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.
Install @angular-package/text package with command:
npm i @angular-package/text --save
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
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.
MIT © angular-package (license)