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.
Sass String - Modified string Sass module.
Extended sass modules:
- The
sass:stringis extended by@angular-package/sass-string- module makes it easy to combine, search, or split apart strings.
Sass extension is free to use. If you enjoy it, please consider donating via fiat, Revolut platform or cryptocurrency the @angular-package for further development. ♥
Feel free to submit a pull request. Help is always appreciated.
This package was generated by the skeleton workspace with Angular CLI version 14.2.0.
Copy this package to the packages/sass-string folder of the skeleton workspace then run the commands below.
Run ng generate component component-name --project sass-string to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project sass-string.
Note: Don't forget to add
--project sass-stringor else it will be added to the default project in yourangular.jsonfile.
Run ng build sass-string to build the project. The build artifacts will be stored in the dist/ directory.
After building your library with ng build sass-string, go to the dist folder cd dist/sass-string and run npm publish.
Run ng test sass-string 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.
The documentation is in construction and it's available at https://docs.angular-package.dev/v/sass-string
To read it, click on the CHANGELOG.md link.
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)
