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

@odoro-cli/server-teams

v0.2.0

Published

Teams for an @odoro-cli/server app: teams, members and roles, invitations by e-mail, in the site's teams database.

Readme

@odoro-cli/server-teams

Teams for an @odoro-cli/server app, stored in the site's own database (the teams capability of odoro-cloud, which needs accounts). Who is signed in comes from @odoro-cli/server-accounts.

  • Teams created by a signed-in person, who becomes their owner.
  • Three roles: proprietaire (everything, including deleting the team), admin (invite, remove a membre), membre.
  • Invitations by e-mail, for one address, seven days, twenty per team per hour. Opening the link proves the address: it signs the person in and makes them a member. An invitation never demotes an existing member.
  • A team always keeps an owner: the last one can neither be demoted nor leave.

The team a request works in is a cookie, checked against the memberships at every request — a cookie never grants a team. whichTeam(db) gives other modules the same answer.

import { createTeamsModule, whichTeam } from '@odoro-cli/server-teams'

const teams = createTeamsModule({ db: pool, mail })
const team = await whichTeam(pool)(cookies) // { id, name, role } | null

A team with room, or without

A site may bound its teams — the seats a team has paid for, for instance. canAddMember(teamId) is asked before an invitation leaves and again before one is accepted: true lets the person in, false refuses with TEAM_FULL, a string refuses with that sentence. A refused acceptance keeps its invitation, which serves once a place frees up. A person already in the team is never asked about.

import { seatsAllowMember } from '@odoro-cli/server-billing'

createTeamsModule({ db: pool, mail, canAddMember: seatsAllowMember(pool) })

A site that serves the invitation link itself calls acceptInvitation(db, token, { canAddMember }): it asks, consumes the invitation, signs the person in and makes them a member.