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

@teliads/pictograms

v1.1.1

Published

Vocads pictograms library

Downloads

5,905

Readme

Pictograms

This package contains the "raw" svg pictograms, that can be used for instance in the telia-pictogram component. It also contains tooling to convert these icons to source code that can be imported and used in your project. The source code is generally based on the raw svg files, and therefore it is not a good idea to change any of the generated source code files manually.

Adding, removing or updating pictograms

If we receive new pictogram svg:s or updated pictogram svg:s of existing pictograms proceed as follows:

  1. Put the new/updated pictogram ./assets/ (not in ./src/assets/!)
  2. Run yarn build

This will re-create the generated source code and therefore also update the actual pictograms.

Removing picrograms is a destructive action that needs to be considered carefully. If an pictogram is removed, it may cause problems for teams who are using that pictogram. Removing an pictogram needs a migration plan. These live in the documentation/ directory of this repository and in the packages/components/src/documentation/ directory. There is information on the Storybook page. (TODO: add link to new storybook site.)

Technically, removing an pictogram only requires you to remove it from ./assets/ and run yarn build.

Source code that is not generated

In the ./src/ directory,

  • utils/
  • global.d.ts

are not generated. These files are either used during the generation of source code, or a part of the dist of this package.