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

@atlaskit/frontend-utilities

v2.7.3

Published

Collecton of small useful frontend utilities

Downloads

14,022

Readme

Frontend Utilities

Collecton of small useful frontend utilities

Utilities

Error Handling

Convert to Error

Network

Retry Operation

Storage

Local Storage mock

Storage Client

Contributing

Anyone is free to contribute a utility that they find themselves copying into multiple packages or that they think will be benefitial to other teams. We just ask that you "own" that slice of this package, ensure it has tests written, and that you add a README stating why and how to use it, as well as what team to contact for more information.

Please put your business logic into 'main.ts' and exports into 'index.ts' as well as a separate entry-point in the package.json.

Then you can update this README and the docs folder. Utility specific documentation can utilise the MarkdownRenderer to render your README file as-is.