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

@dgpholdings/greatoak-shared

v2.0.0

Published

Shared TypeScript types and a few helpers for @dgpholdings projects

Readme

@dgpholdings/greatoak-shared

Types, constants and a few small helpers shared by the Fitfrix mobile app and the admin panel. It contains no algorithms: scoring, calories, records, recovery, the constellation and goal recommendations are computed by the Python backend (fitfrix-be-py), and the app reads their results through the API.

Anything the backend and a client both describe belongs to the API contract (the backend's OpenAPI schema, from which the app generates its request and response types), not to this package. What is left here is what the API does not describe.

What is inside

| Location | Contents | | ------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------- | | src/types/commonTypes.ts | TRecord (the five set types), TExerciseConfig, TTemplateExercise, TDayKey | | src/types/TApiExercise.ts | TExercise, TBodyPart, TBodyPartKeys, TTrainingType, TTimingGuardrails | | src/types/TApiUser.ts, TUserPreferences.ts | TUserMetric and its preference types | | src/types/TApiTemplateData.ts | TTemplate, TTemplateData, TExerciseLatestRecord, TAiPlanContext | | src/types/TApiGoalContextRes.ts | Goal profile, context and recommendation types | | src/types/TConstellation.ts | The constellation as the app receives it | | src/types/TApiAdminAiHelp.ts, TApiAiExerciseAnalysis.ts, adminApi/ | Types used by the admin panel | | src/constants/ | Body categories and names, AI vocabulary (equipment, body areas, injuries, intents), goal and phase display data | | src/utils/ | isDefined, toError, isAnonymousEmail, getDaysAndHoursDifference, weight and height formatting and age (metricConversions) |

Rules

  • No framework code: nothing from React or React Native.
  • Strict types: no any.
  • Do not add algorithms here. A rule about workouts belongs in the backend.

Renewing token

  1. Login using the token (recommended way)

In your Git Bash, run:

npm login

It will prompt:

Username: Password: Email:

Use this:

Username → your npm username

Password → paste the granular token (NOT your npm password)

Email → your npm email

After that, npm stores the token in:

shared\.npmrc

Then publishing works normally:

npm publish