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

@livdot-tech/contracts

v1.8.0

Published

Shared API contracts for the LivDot platform

Downloads

4,172

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

c.arilc.arillivdotlivdot

Keywords

Readme

LivDot Shared Contracts

Central contract repository for schemas and shared API-facing types used across the LivDot platform.

Purpose

This repository exists to keep backend, frontend, and mobile aligned on the same contract surface without coupling the codebases into a monorepo. It is the single shared source for:

  • request and response schemas
  • domain enums and state constants
  • canonical error codes
  • shared DTOs and validation rules
  • other API-boundary definitions that must remain consistent across services and clients

Repositories That Consume This Package

  • livdot-backend
  • livdot-frontend
  • livdot-mobile

What Belongs Here

Only cross-stack contract artifacts. Examples:

  • CreateEventRequest
  • BookingStatus
  • EventLifecycleState
  • ApiErrorCode
  • Zod schemas for payload validation
  • shared auth/token payload shapes where applicable

What Must Not Be Added Here

This repository is not a dumping ground for shared code. Do not add:

  • backend business logic
  • ORM/database models
  • repositories/services/use-cases
  • frontend UI components
  • mobile-specific runtime code
  • infrastructure or deployment logic
  • utilities that are not part of a cross-stack contract If it is not part of the contract boundary, it does not belong here.

Ownership

The backend remains the authority on system behavior and API truth. This repository defines the contract shape, not the implementation or business logic.

Versioning

This package must follow semantic versioning:

  • PATCH: backward-compatible fixes
  • MINOR: backward-compatible additions
  • MAJOR: breaking changes Consumer repositories must pin explicit versions and upgrade through review.

Change Rules

Any contract change must be treated carefully because it can affect multiple codebases. Before merging a change:

  1. confirm the change is truly cross-stack
  2. identify whether it is breaking or non-breaking
  3. update version appropriately
  4. document migration notes if consumers need code changes

Recommended Structure

src/
  auth/
  booking/
  common/
  errors/
  event/
  payment/
  index.ts

Installation and Usage

See README.md.

Goal

Keep contracts explicit, versioned, and stable.

This repository exists to improve consistency across backend, frontend, and mobile while preserving clear ownership boundaries between the separate LivDot codebases.