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

@meta-inf/forge-logger-resolver

v0.4.2

Published

This package contains the Resolver part of the Forge Logger, which is a simple yet powerful logger for Atlassian Forge apps.

Readme

META-INF Forge Logger - Resolver

This package contains the Resolver part of the Forge Logger, which is a simple yet powerful logger for Atlassian Forge apps.

Installation

yarn add @meta-inf/forge-logger-resolver

Usage

Define the resolver in order to use the React logger

import Resolver from '@forge/resolver';
import {defineLogResolver} from '@meta-inf/forge-logger-resolver';

const resolver = new Resolver();

defineLogResolver(resolver); // <--- Add this line

export const handler = resolver.getDefinitions();

Use logger functions inside your backend resolvers

import {createLogLocation} from "@meta-inf/forge-logger-resolver";

const {log, logError, logWarn, logInfo, logDebug} = createLogLocation('my-log-location');

New, more convenient way to log messages

There is a more convenient way to log messages. You can initialize the Logger class statically, which will add a click event listener to the document. When you click on an element, the logger will log the element's location in the DOM, if it has a data-location (or the provided) data attribute.

In your entry file (index.tsx or main.tsx), initialize the Logger class statically.

Logger.init();
// or
Logger.init({
    dataFields: ["location", "test-id"] // default is ["location"]
})

Example: when a user clicks on a button that has a data-location attribute with the value my-button, the logger will log my-button as location with a 'Clicked' event.

However, if you have onClick listeners on the button, the events won't propagate to the document, and the logger won't log the location. In this case, you can use the withClickTracking wrapper function, which will log the event accordingly, and then call the original function.

There is also a withChangeTracking function, which logs the event when the input value changes.

import {withClickTracking, withChangeTracking} from "@meta-inf/forge-logger-react";
<button
    data-location="modal-trigger"
    onClick={withClickTracking(openModal)}>
    Open modal
</button>

Configuration

The logger can be configured by passing a configuration object to the defineLogResolver function.

import {defineLogResolver} from "@meta-inf/forge-logger-resolver";

defineLogResolver(resolver, {
    functionKey: 'my-log-key', // The function key to use in the resolver, defaults to '@forge-logger-send-log'
});