npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@angular-package/sass

v0.19.0-beta

Published

Extension for sass modules and new modules.

Downloads

23

Readme

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.

Gitter Discord Twitter

npm version

GitHub issues GitHub forks GitHub stars GitHub license

GitHub Sponsors Patreon Sponsors

Extended sass modules:

New modules:

Module moved:

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.

Table of contents

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

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.

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.

License

MIT © angular-package (license)