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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gotamedia/utils

v0.1.2

Published

Set of Utils helper for NodeJs Runtime.

Readme

Gota Media Utils

Set of Utils helpers for NodeJs Runtime.

Usage

npm install @gotamedia/utils
import { logError } from "@gotamedia/utils/logError"

const handler = () => {
    logError(new Error("Oops!"))
}

Utils

Available utils:

  • logError
  • getErrorTrace
  • sourceMapSupport

Available methods:

logError()

A helper function to log errors with traces

| param | type | default | required | description | |--------|-------|-----------|----------|----------------------------------------------------------------------------| | first | Error | undefined | | Error object to parse and log with traces | | second | any | undefined | | Any additional info that will be added to the output under ìnfo property |

Example:

import logError from "@gotamedia/utils/logError"

const handler = async () => {
    const trakingId = "123-321"

    try {
        ...
        const response = await fetch(`www.example.com/id/${trakingId}`)
        ...
    } catch (error) {
        logError(
            error,
            {
                trakingId: trakingId,
                message: "Oops! Something went wrong here.",
                reason: "Failed to do something because of something"
            }
        )
    }
}
getErrorTrace()

A helper function to extract trace from Error object

| param | type | default | required | description | |--------|-------|-------------|----------|------------------------------------| | first | Error | new Error() | | Error object to extract trace from |

Example:

import { getErrorTrace } from "@gotamedia/utils/getErrorTrace"

const handler = async () => {
    try {
        ...
    } catch (error) {
        const trace = getErrorTrace(error)

        console.log(trace)
    }
}
sourceMapSupport

A helper util to parse source-maps from your "un-minified" Lambda code if you bundle and minify your Lambda

NOTE: If you want to support source-map this import needs to be the first import statement in your entry file.

Example:

import "@gotamedia/utils/sourceMapSupport"

const handler = async () => {
    ...
}

Contributing

Trunk based development

This project uses a trunk based development workflow.

NOTE: master is the trunk branch

Conventional commits

This project works with conventional commits.

Contribute

  • Pull latest from develop.
  • Branch out a new branch.
  • Commit and push your awesome code.
  • Open a pull request so we can approve your awesome code.

Publish

Any time you push to origin master branch, a pipeline will be automatically triggered and it will build the package for you. The pipeline will bump the version for you automatically and tag the package.

NOTE: NO MANUAL TAGGING

Then it will generate and update the CHANGELOG depends on your pushed commits.

License

MIT