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

@nfcard/card3d

v0.1.0

Published

Real-time 3D card render core for NFCard (plain Three.js) — shared by the web 3D preview and the print-station kiosk.

Downloads

53

Readme

@nfcard/card3d

The real-time 3D card render core, as plain Three.js (no React). Hand it a canvas and a CardDesign; it owns the renderer, camera, lighting (IBL), the perforated card mesh, PBR materials + procedural relief, and the content decal (text / wordmark / QR / logo).

It is shared, unforked, between two front-ends:

  • nfcard-web — the React Card3DView wrapper (stays in the web app) mounts this core for the in-configurator 3D preview.
  • nfcard-station — the Tauri print kiosk calls buildCardScene directly from vanilla TS for an always-on high-tier preview (NFCARD-229 / T3).

Hole geometry is not duplicated here — it comes from @nfcard/pattern-engine, the same engine the 2D configurator uses.

Public API

import { buildCardScene, detectTier } from '@nfcard/card3d'

const tier = detectTier()                 // 'low' | 'mid' | 'high' (+ QualityProfile)
const scene = buildCardScene(canvas, design, { profile: tier })
// scene: CardSceneController — { update(design), resize(), dispose(), ... }

| Export | Purpose | | --- | --- | | buildCardScene(canvas, design, opts)CardSceneController | Full scene: renderer + camera + lights + render loop | | buildCardMesh / disposeCardMesh | The perforated card mesh on its own | | buildCardMaterial, reliefFromCardgen | Per-material PBR + relief | | buildFieldReliefTexture | Procedural decorative relief → normal map | | buildContentDecal | Text / wordmark / QR / logo onto the face | | detectTier, isMobile | Device capability → quality profile | | SAMPLE_CARD_DESIGN, DENSE_CARD_DESIGN, CONTENT_CARD_DESIGN | Demo fixtures |

three is a peer dependency (>=0.176) so the host app owns the single Three.js instance — install it alongside this package.

Render parity

This is the preview renderer (the TS pattern engine). Manufacturing geometry comes from cardgen (Python). The two are intentionally distinct — the relationship gated by NFCARD-172 — so a 3D preview is representative, not a manufacturing source of truth.

Build

pnpm build   # tsup → dist/index.js (ESM, three/qrcode external) + dist/index.d.ts