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

@financial-times/fticons

v1.23.1

Published

This is the (new) icon set for FT websites. It replaces the assets in [o-icons](http://github.com/financial-times/o-icons).

Downloads

1,050

Readme

Icon set for FT

This is the (new) icon set for FT websites. It replaces the assets in o-icons.

The icons have been designed to work best at 40px width and height. At this size they align precisely with the pixel grid and do not appear blurry on screens with a DPR of 1 (non-retina screens).

Index

Usage

You can use fticons in the following ways:

  1. You can access them directly from the Image Service, eg https://www.ft.com/__origami/service/image/v2/images/raw/fticon-v1:podcast?source=test
  2. There is also an Origami component that wraps this icon set: o-icons. As with all Origami components, you can use o-icons with the Build Service, or as an installable component. See the o-icons README for more information.

Creating or modifying new icons

Please check out our contributing guide for design and development guidelines for adding or modifying icons.

SVG icons GOTCHAs

My icons are blurry!

All of our icons are vectors. At small sizes, the process of converting a vector to a bitmap (rasterization) will leave you with with blurry icons. All of the icons in fticons have been drawn to map precisely to a 40x40px grid. If you need to use these at a smaller or larger size, they may appear fuzzy as the browser tries to anti-alias them.

I'm exporting my icons at 40px and they should work but they're still fuzzy!

Sometimes sketch will export icons with rounding errors, so if you think you're exporting them on the correct grid and they're still blurry, open the source and look if the path points are values like 372.00000001. The fix for this is to either:

  • not use sketch
  • hand edit your SVGs to remove these errors

When I convert my icons to PNG, they're blurry!

This will happen if the source SVG is smaller than the size you're converting to. This is because the Image Service converts the format first and then resizes, resulting in blurriness. The solution is to make sure your source SVGs have a width and height bigger than the size they're likely to be used at.

My icon is not converting to a PNG properly

If your icon has a clipPath in it, then with v1 of the Image Service, it may not render properly. Usuallt it will look like the clipPath isn't there. To fix this you'll need to redraw your icon without the clipPath.

Migrating from o-icons assets

If you were using the old o-icons assets, some things have changed in this new set.

The whitespace around icons has now been standardised. This means that some of the padding may have changed, so if your code inserts and icon to line up with some other stuff, you should check that still works, you may need to adjust it.

Removed

The following icons no longer exist:

  • arrow-downwards (use arrow-down)
  • arrow-upwards (use arrow-up)
  • comment (use speech)
  • cross-disk (use cross)
  • pinterest (social icons are used differently, please use the ones in bitbucket: http://git.svc.ft.com/projects/DATA/repos/social-images/browse)
  • section-business-life
  • section-magazine
  • single-quote-patterned (use speech-left)
  • single-quote (use speech-left)
  • thumb-up (please let us know if you need this back)
  • tick-thin (use tick)

Renamed

  • arrow-up-down to arrows-up-down
  • bell to notification
  • copy-link to link
  • email to mail
  • ipad-portrait to ipad
  • padlock to lock
  • printer to print
  • pullquote to speech-left
  • speechbubble to speech

What happened to o-icons

o-icons still exists, and provides Sass mixins to use icons with. In order to properly version the icon set we've moved it to it's own repo (this one). This means we can do major releases of o-icons Sass without needing to bump the icon set (which can be accessed independently of o-icons via the Image Service.)


Contact

If you have any questions or comments about this component, or need help using it, please either raise an issue, visit #origami-support or email Origami Support.


Licence

This software is published by the Financial Times under the MIT licence.