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

@open-pioneer/core

v4.7.0

Published

Contains basic utility functions and classes used by the @open-pioneer project.

Readme

@open-pioneer/core

This package contains basic utility functions and classes used in Open Pioneer Trails applications.

Usage

Errors

The Error class extends JavaScript's global error class with a user defined id value that can be used to explicitly identify error conditions.

import { Error } from "@open-pioneer/core";
throw new Error("my-error:identifier", "This is the error message");

Error also exposes the optional cause attribute that allows nesting of error instances. Note that browser support for that property is still required:

import { Error, getErrorChain } from "@open-pioneer/core";

try {
    someFunctionThatCanThrow();
} catch (e) {
    throw new Error("my-error:higher-level-error-id", "Error text", { cause: e });
}

// getErrorChain gathers the error and all its causes (if any) into an array:
const errors = getErrorChain(error);

Resources

The Resource type exported from this package is used by objects with a destructor. All object needing some cleanup action to be called should use the destroy method for consistency and easier handling.

Logger

The Logger class provides a logger for standardized application wide logging. The log level is configured globally in the file vite.config.ts: to change the application's log level, define the __LOG_LEVEL__ constant to a custom value.

To create a logger instance, call the createLogger method. It takes a prefix (string) to prepend to each message. To encode hierarchical names, use : as a separator (for example "some-package:SomeClass").

The logger provides log methods for the following log levels with the following order: DEBUG < INFO < WARN < ERROR.

For example (as class attribute):

import { createLogger, Logger } from "@open-pioneer/core";

export class LoggerTestExample {
    private logger: Logger;
    constructor() {
        this.logger = createLogger("example-package:LoggerTestExample");
    }

    testMethod() {
        this.logger.warn("example message", { testLog: 123, text: "this is a text" });
    }
}

Or as a shared logger at module scope:

import { createLogger } from "@open-pioneer/core";
const LOG = createLogger("example-package");

With recent version of the trails vite plugin, you can also use this convenient way to create a logger:

import { sourceId } from "open-pioneer:source-info";
// sourceId is an automatic identifier based on the current file.
const LOG = createLogger(sourceId);

Deprecations

The deprecated function can be used to print warnings when a deprecated entity is used. Deprecations are printed (once) during development, and not at all in production. You can disable deprecations via the global configuration in vite.config.ts: set __PRINT_DEPRECATIONS__ to false to hide deprecation messages even during development.

To emit a deprecation warning, create a helper function through the deprecated function. Then, when the deprecated functionality is being used, simply call that helper function:

const printDeprecation = deprecated({
    name: "someFunctionName",
    packageName: "some-package",
    since: "v1.2.3",
    alternative: "use xyz instead"
});

// Later, when the deprecated function is actually being used:
function someFunctionName() {
    printDeprecation(); // prints warning on first call
    // ...
}

Events

Note: the EventEmitter class is deprecated since v4.2.0. Use @conterra/reactivity-events instead.

The package exports the EventEmitter class that supports emitting and subscribing to user defined events.

Equality functions

Use shallowEqual and deepEqual to compare two generic objects. Note that the functions are intended to be used with plain old data (i.e. mostly JSON).

They do not support cycles.

Examples:

import { shallowEqual, deepEqual } from "@open-pioneer/core";

shallowEqual({ a: 1 }, { a: 1 }); // true
shallowEqual({ a: { x: 1 } }, { a: { x: 1 } }); // false
deepEqual({ a: { x: 1 } }, { a: { x: 1 } }); // true
deepEqual([1, [2, 3]], [1, [2, 3]]); // true

License

Apache-2.0 (see LICENSE file)