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

comet-widget

v1.5.1

Published

Comet drop-in widgets library

Downloads

58

Readme

comet-widget

Comet drop-in widgets library

This is an npm package

Use

You can install comet by running

npm i comet-widget

Then imported as:

import { Comet } from 'comet-widget';

Finally drop it in any page you want:

<Comet context={<context>} entityId={<entityId>} relatedEntities={<entityId[]>} />

where:

  • context is the scope on which you want to add a comment to an entity
  • entityId is the main entity to which you want to add the comment, eg: policy-administration, motor-certificates, bonus-malus-ownership, ...
  • relatedEntities are entities closer to the main one that are used to build the "magic links" jira, confluence, ...

You can also import the modal and button component separately from the widget:

import { Trigger, Modal } from 'comet-widget'

These are useful when you want to handle some states in the parent service, e.g: building a button that spawns many modals, but you only want one modal open at a time.

Development

Local development requires a bit of npm magic to make it work.

For example to run a local version of Comet against Heimdall we need to do the following:

  • In memo-widget run npm link to create a local version of the package and npm run watch to rebuild the library after changes
  • If you are using Vite you need to run vite --force, so in Heimdall run npm link comet-widget && npm run start:force, this will force re-optimization of dependencies and pick up the local one
  • If not run npm link comet-widget && npm run start

Publishing

At the moment, publishing is a manual task. For that, you have to:

  • Run npm login. Credentials can be found in Integrations 1Password Vault
  • Bump the version with npm version <patch|mintor|major>
  • Publish the package with npm publish