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

@manwaring-games/codenames-common

v0.0.10

Published

Common interfaces for UI and API/services

Downloads

21

Readme

Codenames common library

This repository contains TypeScript interfaces for the Codenames application, for use by both frontend and backend projects.

Install

npm i -S @manwaring-games/codenames-common

Local development

Local setup prerequisites

  1. CircleCI CLI: This project uses CircleCI for CI and publishing, and contains a Git hook (managed by husky) to validate the CircleCI config before committing. For you to commit changes you'll need to install the CLI.
  2. Nodejs: I recommend using nvm or something similar to manage Node versions locally. This project is developed and tested on the lts version, which as of inital package publishing is 12.16.3.

Steps to publish

  1. Commit changes locally
  2. Update package version (using semantic versioning) with the npm version <version> command and commit the updated package.json and package-lock.json files
  3. Push all changes to GitHub
  4. *Create a new release in GitHub matching the new package version, prefixed with a v e.g. v0.0.1

*Note that commiting to the main branch will trigger CI checks in CircleCI but won't initiate package publishing - only the creation of a new release in GitHub will initiate the CircleCI workflow to publish a new package.