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

@meltwater/conversations-api-services

v1.3.2

Published

Repository to contain all conversations api services shared across our services

Readme

conversations-api-services

Repository to contain all conversations api services shared across our services.

Maintainers

Maintained by Phoenix ([email protected]). Contact us via #eng-team-phoenix in Slack.

Contributing

Make it easier for people to understand how they can contribute to your project. Remember that these people could be from your own team, or another team.

Example:

We welcome and appreciate any and all contributions, even if it is a typo fix to this README. When working on a larger contribution, please open an issue first, so that we can discuss the approach. Once you have your contribution ready, please open a Pull Requests containing your changes and contact us via #TEAM_SLACK_CHANNEL in Slack.

How do I use it? (Installation)

Instructions targeted at the user of your project, rather than at a co-developer in your team. This section should answer:

How to use this?

If this is an internal tool that is just used within your team, then you can share this here as well.

Development Guide

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. This section should answer:

How to get started with developing on this project?

This is essential for onboarding new members on your team but also for allowing people from outside of your team to contribute.

This Development Guide may contain different sub-sections, depending on what stack/ecosystem your project is using. Below some examples of sub-sections that apply to most projects.

Prerequisites

What things do you need to install the software and how to install them? Including links here is helpful.

Running it locally

A step-by-step series of examples that tell you how to get a development env running.

End with an example of getting some data out of the system or using it for a little demo.

Running the tests

Explain how to run the automated tests for this system.

Deployment

Add additional notes about how to deploy this on a live system. You may also want to link to the different environments where this is deployed (e.g. Staging, Production).

Monitoring & Troubleshooting

How can you inspect the system running in remote environments (Staging, Production)? This should include logs, dashboards, etc.