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

@smartregionlab/cop-types

v1.0.6

Published

Shared TypeScript types for frontend and backend

Readme

cop-types

This repository acts as an unpublished npm package that can be consumed by other applications. It contains a collection of types that are shared among the cop applications, using the cop-backend application as a baseline. Any types that are not needed in the backend application will not be published to this repository, and need to be implemented locally.

Publishing/Changing types

  1. Clone the git repository
git clone [email protected]:hslu/research/infovis/smartregion/pilots/cop/cop-types.git
  1. Move into the newly downloaded repository
cd cop-types
  1. Add/update/remove the type from the src/*-types.ts file
const SamplePodcastSchema = z.object({
  id: z.string(),
  title: z.string(),
  description: z.string(),
  authorId: z.string(),
  createdAt: z.date(),
});

export type SampleZodPodcast = z.infer<typeof SamplePodcastSchema>;

(Ensure to update any corresponding exports)

  1. If a new file was created, update the exports in src/index.ts

  2. Push the new version to the main branch

git add .
git commit -m "chore: added podcast type"
  1. Bump the npm package version ("version": "X.X.X"), using the npm utility:
  • For minor changes/bug fixes: npm version patch (change of 0.0.1)
  • For bigger changes/new types: npm version minor (change of 0.1.0)
  • For breaking changes: npm version major (change of 1.0.0)

The npm version utility updates package.json, package-lock.json and creates a new git tag with the updated version. It also creates a new git commit locally.

  1. Publish the updated version
npm publish
  1. Push the updated files to remote
git push origin main
git push --tags

Consuming types

  1. Install the type package from source
npm install @smartregionlab/cop-types
  1. Update an already installed version of the package
# Update all packages
npm update

# Pull newest version of only the cop-types package
npm install @smartregionlab/cop-types@latest

# Install specific version i.e. 1.2.3
npm install @smartregionlab/[email protected]
  1. Import and use the type in the current .ts file
import { SampleZodPodcast } from "@srl/cop-types"

const podcast: SampleZodPodcast = {
  id: "123",
  title: "My Podcast",
  description: "A show about coding",
  authorId: "author-1",
  createdAt: new Date(),
};

In this case, Zod will now ensure runtime typesafety through the external cop-types package. If we define something that is not allowed, ie:

const podcast: SampleZodPodcast = {
  id: "123",
  title: "My Podcast",
  description: "A show about coding",
  authorId: "author-1",
  createdAt: "a string instead of a date",
};

Zod will throw an error:

error TS2322: Type 'string' is not assignable to type 'Date'.