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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@atb-as/utils

v6.0.0

Published

Shared utility methods and types for AtB products

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

marius-at-atbmarius-at-atbmikaelbmikaelbatb-martinatb-martingorandalumgorandalumrosvikrosvikabelvanbeekabelvanbeeknshrautelanshrautelamortennordsethmortennordsethreidzeibelreidzeibelhanne-at-atbhanne-at-atbjorelosoriojorelosoriojonasbl_mittatbjonasbl_mittatbadriansbergadriansbergstrandliestrandliejorunn-at-atbjorunn-at-atbmagnudahmagnudah

Keywords

Readme

@atb-as/utils

Shared typescript utility methods and types for AtB products.

Install

yarn add @atb-as/utils

Local development

In order to test local changes to the package locally, you can use yalc. This is an alternative to yarn link, that works better with React Native / metro.

  1. Run npm i yalc -g to install yalc on your machine.
  2. Run yarn build && yalc push to set up a local link to this package.
  3. Run yalc add @atb-as/utils in the project that depends on it.

Your local changes to @atb-as/utils should now be available to use. When you make more changes locally, you can run yarn build && yalc push again to update the linked package.

When you're done, run yalc remove --all to reset the project's package.json.

Release

  1. Merge a PR to main, where the commit message follows the conventional commits specification.
  2. The Github action release-please-action will create a PR to update the package version and changelog.
  • feat will be a minor release.
  • fix will be a patch release.
  • Adding ! after the prefix (e.g. feat!) means it is a breaking change, and will be a major release. This includes any changes to the public API that requires users of the package to update any code.
  • Other prefixes such as chore or refactor will not trigger a release.
  1. Merge the release PR to main to trigger a NPM release.

[!NOTE] In case you want to create a release with a different version number than the one suggested by release-please, you can make an empty commit on master with commit message on this format:

chore: release v1.2.3

release-as: 1.2.3

For more details, see release-please-action.

License

EUPL-1.2