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

@mantis-core/utils

v0.3.0

Published

Reusable framework-agnostic utility helpers for Mantis Core.

Downloads

321

Readme

@mantis-core/utils

Scalable utility toolkit for Mantis Core with runtime-specific modules.

See architecture governance in ARCHITECTURE.md.

Scope

  • Shared reusable helpers for all Mantis Core apps/packages.
  • Strong TypeScript contracts (Result, branded types, generic helpers).
  • Runtime-separated APIs for safer imports:
    • isomorphic (@mantis-core/utils)
    • browser-only (@mantis-core/utils/browser)
    • node-only (@mantis-core/utils/node)

Out Of Scope

  • Domain/business logic (real estate, leads, blog workflows).
  • Supabase repositories/actions.
  • Next.js route-specific behavior.

Folder Architecture

src/
  index.ts              # isomorphic public API
  types.ts              # shared advanced types
  isomorphic/
    index.ts
    classnames.ts
    select.ts
    date.ts
    currency.ts
    base64.ts
    sanitize-html.ts
  browser/
    index.ts
    device.ts
    events.ts
  node/
    index.ts
    crypto.ts

Public API

1) Isomorphic (@mantis-core/utils)

  • cn(...inputs)
  • getFilterValue(...)
  • toStartOfDayIso(...)
  • toEndOfDayIso(...)
  • getPaginationRange(...)
  • formatCurrency(...)
  • encodeBase64Json(...)
  • decodeBase64Json(...)
  • decodeBase64JsonOrThrow(...)
  • sanitizeHtmlContent(...)
  • types: Brand, Result, JsonValue, MaybeArray, ValueOf

2) Browser (@mantis-core/utils/browser)

  • isIOSDevice(...)
  • isInStandaloneMode(...)
  • isPwaInIOS(...)
  • createClickIntentHandler(...)
  • simulateTouch(...)
  • setViewportHeightCssVar(...)

3) Node (@mantis-core/utils/node)

  • hashString(...)
  • toSha512(...), toSha256(...), toSha1(...), toMd5(...)
  • generateRandomString(...)
  • isAes256KeyHex(...)
  • assertAes256KeyHex(...)
  • encryptAes256Cbc(...)
  • decryptAes256Cbc(...)
  • types: HexDigest, Aes256KeyHex

Import Rules

  • Use root import for cross-runtime helpers:
    • import { formatCurrency } from "@mantis-core/utils";
  • Use explicit runtime subpaths for platform APIs:
    • import { toSha512 } from "@mantis-core/utils/node";
    • import { isPwaInIOS } from "@mantis-core/utils/browser";

Do not import node helpers in client bundles.

Build

pnpm --filter @mantis-core/utils build
pnpm --filter @mantis-core/utils typecheck

Scalability Rules

  1. Place a utility by runtime first:
    • src/isomorphic/*: can execute in browser and Node.
    • src/browser/*: requires window, document, navigator, Touch*.
    • src/node/*: requires Node built-ins (node:*, Buffer, filesystem/crypto APIs).
  2. Keep functions single-purpose and side-effect free when possible.
  3. Prefer explicit return contracts (Result, branded types, discriminated unions) over thrown errors for recoverable failures.
  4. Do not add domain/business vocabulary (houses, leads, blog workflows).
  5. Any new utility must include:
    • named export from its runtime index.ts
    • README usage update if it is part of public API
    • package build/typecheck passing