1.0.0 • Public • Published


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 - extension for sass modules and new modules.

Gitter Discord Twitter

npm version

GitHub issues GitHub forks GitHub stars GitHub license

GitHub Sponsors Patreon Sponsors

Extended sass modules:

New modules:

Module moved:


In the beta version, two translators are inside the translator folder. First(will be deprecated) v0.1.0, the default exported dictionary, was created to pass an external dictionary in some functions to merge with a global dictionary. The second, newer, and simplified translator v1.0.0 is designed with only the global(internal) dictionary, and the external dictionary is passed only in merge and translation.

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.

Table of contents


This package was generated by the skeleton workspace with Angular CLI version 14.0.0.

Copy this package to the packages/sass folder of the skeleton workspace then run the commands below.

Code scaffolding

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

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


Run ng build sass to build the project. The build artifacts will be stored in the dist/sass directory.


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

Further help

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


To read it, click on the CHANGELOG.md link.




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.


MIT © angular-package (license)

Package Sidebar


npm i @npmtuanmap2024/reiciendis-eos-magnam

Weekly Downloads






Unpacked Size

970 kB

Total Files


Last publish


  • npmtuanmap