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

@hafslundnett/hdd-style

v10.0.2

Published

A universal design system used across Hafslund nett

Downloads

104

Readme

Hafslund digital designsystem (Hdd)

npm version npm size Commitizen friendly githubActions

'Hafslund digital designsystem' is a design system that can be used across projects while maintaining consistancy. The project follows strict naming guidlines, your can read more about them in the wiki. Every component should be able to run in an isolated environment without depending on parent classes/elements.

For every used front-end framework a separate 'components' library should be created. Listed below are the already existing libraries. If you want to add your library to this list, please create a pull request.

| Framework | Version | Repo | | ------------- | ------------- | ------------- | | Angular 6.x | 🚧 Alpha | Github | | Vue 2.x | 🚧 Alpha | Github |

Documentation

HDD-style is documented along with it´s corresponding components library(HAL) at:

  • https://hal-components.hafslundnett.io

The showoff website include all documentation off components with related examples. The showoff website can be generated/started by running:

  • yarn
  • yarn start

You need to have node and yarn installed in order to start the showoff website.

Publish new version

You need access to the Hafslund Nett NPM organisation

  • yarn build
  • npm publish

Code of conduct

We will behave ourselves if you behave yourselves. For more details see our code of conduct.

Contributing

Please read through our contributing guidelines.

Versioning

This project will be maintained under the Semantic Versioning guidelines as much as possible. Releases will be numbered with the following format:

<major>.<minor>.<patch>

Releasing new versions and updating CDN

Azure CDN is used to host fonts and icons from the cdn/ folder. To update the contents of

  1. Check in the new files under cdn/.
  2. If this will be included in a new version of the package: Update the package version in package.json and the CDN-url in variables/fontawesome/_variables.scss. The three numbers after "hdd-style-release-" should match the package version. If the package version is 1.0.2, then the url bound to $fa-font-path should be https://hafslundnett.azureedge.net/hdd-style-release-1-0-2/icons.
  3. Check in and get your pull request accepted into develop.
  4. Create a new release-branch and push it to GitHub. The name of the branch should be on the format release/1.0.2, given that the package version is 1.0.2. This will start the hdd-style.release build, and upload the contents of cdn/ to Azure CDN.
  5. Continue to release the new version of hdd-style by packaging and uploading the new version to npm manually.
  6. When everything is ok, merge the release-branch into master, and draft a new release on GitHub.

Note: This process has room for improvements.

Team