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

@telenorfrontend/tn-components

v0.1.2

Published

Component library for components used throughout Telenor

Downloads

16

Readme

Build Status

Telenor Frontend Component Library

Live at https://telenorfrontend.github.io/component-library/

Getting started

Before you start, make sure you have a recent version of NodeJS environment >=8.0 with NPM 5.x

From the project folder, execute the following command:

npm install

Also make sure that you have gulp installed globally by installing it with the command:

npm install gulp-cli -g

When done, you will have installed all required dependencies.

To run the styleguide in watch mode execute the following command:

npm run watch

This command starts the styleguide and compiles the current scss-files into the stylesheet. The styleguide will be available at http://localhost:8888. Changes in the scss will automatically build and reload the styleguide.

Adding your first component

Before you start adding a new component familiarize yourself with Nucleus by reading their getting started section of annontations. To add a new component, simply add a new file to the components folder which ends in .scss. This will make gulp react to your file and start parsing it accordingly.

Running The Tests

To ensure code quality we run linting on all scss-files. To run linting execute:

npm test

All lint warnings and errors (if any) should now appear in the console.

Committing and releasing

Commit guidelines

When commiting code for the repo you will need to use the conventional commits guidelines. This will be validated upon commit and helps us in several ways. It keeps a clean git history and helps creating a useful CHANGELOG when running a release.

Releasing new version

We use standard-version instead of the conventional npm version due to it's connection to conventional commits and the ability to create CHANGELOG automagically.

To release a new version you can simply type

npm run release

This will make standard-version go through the commits and decide for itself what kind of version bump is needed (major, minor and patch). However, sometimes it's easier to explicitly state what kind of version you want to bump. To help with this, we've added three simple abstractions

npm run release:patch
npm run release:minor
npm run release:major

Release example

You want to release a minor version of the repo.

  1. Add all your commits
  2. Run npm run release:minor
  3. Chore step:
  • Run npm i
  • Run git add package-lock.json
  • Run git commit -m "chore(package-lock): bump version"
  • This step is due to the changing version number of package-lock after you bump the package.json.
  1. Run git push --follow-tags origin master
  2. (Optional) Run a npm publish

FAQ

How do I enable stylelint in Intellij IDEA?

  • Open Preferences
  • Search for stylelint (or go to Languages & Frameworks > Stylesheets > Stylelint)
  • Click Enable

How do I enable stylelint in VS Code?

  • Open project in Code
  • A list of recommended plugins will pop up, for optimal dev environment add all
  • Success