@angular-package/sass NPM

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.

Sass

Sass - extension for sass modules and new modules.

Extended sass modules:

The sass:color is extended by @angular-package/sass/color - module generates new colors based on existing ones, making it easy to build color themes.
The sass:list is extended by @angular-package/sass/list - module lets you access and modify values in lists.
The sass:map is extended by @angular-package/sass/map - module makes it possible to look up the value associated with a key in a map, and much more.
The sass:math is extended by @angular-package/sass/math - module provides functions that operate on numbers.
The sass:meta is extended by @angular-package/sass/meta - module exposes the details of Sass’s inner workings.
The sass:selector is extended by @angular-package/sass/selector - module provides access to Sass’s powerful selector engine.
The sass:string is extended by @angular-package/sass/string - module makes it easy to combine, search, or split apart strings.

New modules:

The @angular-package/sass/class module to handle CSS class selectors(variants).
The @angular-package/sass/comparison module to compare single or multiple values.
The @angular-package/sass/function module function to handle calling functions, especially in a form of string in list.
The @angular-package/sass/media module to handle @media CSS at-rule.
The @angular-package/sass/object module to handle sass variable of map type as named objects.
The @angular-package/sass/property module to set multiple CSS properties or variants with called functions on values.
The @angular-package/sass/query module to execute query on list to retrieve data.
The @angular-package/sass/translator module handles global dictionary to translate words.
The @angular-package/sass/values module to modify arbitrary values.
The @angular-package/sass/var module is designed to handle CSS variables with the use of words that can be translated by the dictionary.
The @angular-package/sass/variant module to create variants usable in class and property modules.

Module moved:

The @angular-package/sass/number moved to the @angular-package/sass/math module.

Translator:

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.

Skeleton

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

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

Build

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

Publishing

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.

Documentation

The documentation is in construction and it's available at https://docs.angular-package.dev/v/sass

Changelog

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

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.