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

@kie-tooling-core/notifications

v0.16.0

Published

This package provides a type-safe Notifications library for a Typescript project.

Downloads

195

Readme

Kogito Tooling Notifications

This package provides a type-safe Notifications library for a Typescript project.

Install

Can be installed with yarn or npm:

  • yarn add @kie-tooling-core/notifications
  • npm install @kie-tooling-core/notifications

Usage

The library is separated into two submodules:

  • api All the APIs and the main classes needed are in this submodule.

    to use the core:

    • import { NotificationsApi } from "@kie-tooling-core/notifications/dist/api"
    • import { Notification } from "@kie-tooling-core/notifications/dist/api"
    • import { NotificationSeverity } from "@kie-tooling-core/notifications/dist/api"
    • import { NotificationType } from "@kie-tooling-core/notifications/dist/api"
  • vscode

    All the classes needed to use in vscode channel implementation

    to use the vscode classes:

    import { VsCodeNotificationsApi } from "@kie-tooling-core/i18n/dist/react-components";
    
    const api: NotificationsApi = new VsCodeNotificationsApi(workspaceApi, i18n);

API

NotificationsApi main attributes:

  • messages: The text that will be shown to the user
  • path: File location.
  • severity: "INFO" | "WARNING" | "ERROR" | "SUCCESS" | "HINT"
  • type: "PROBLEM" | "ALERT"

VS Code

The VsCodeNotificationsApi is the only "public" class users have access. Under the hood it contains two different implementations depending on Notification.type.

So if:

  • Notifications.type === "PROBLEM" The notifications are going to be shown in Problems Tab.
  • Notifications.type === "ALERT" The notifications are going to be shown as Popups.

If, for some reason, there is not type, the default is PROBLEM

In both cases path is mandatory and it will let the user to open the file where those notifications come from.

Notification.severity also depends on Notification.type, if:

  • PROBLEM, the supported severities are "INFO" | "WARNING" | "ERROR" | "SUCCESS" | "HINT". SUCCESS converts to INFO which is the default severity.
  • ALERT, the supported severities are "ERROR" | "WARNING" | "INFO". Any other types defaults to INFO