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

@thejob/resume-render

v1.11.0

Published

The resume renderer shared by thejob and the standalone resume builder: templates, pagination and HarfBuzz line breaking, identical in every browser and in the PDF.

Readme

@thejob/resume-render

The one resume renderer, shared by thejob (thejob-svelte-ui) and the standalone resume builder (resume-builder-ui). resume-service's PDFs are each app's print route running this in Chromium, so preview and PDF match.

<script>
  import { ResumePaged, TemplateThumb } from '@thejob/resume-render';
</script>

<ResumePaged {resume} {labels} {levels} lang="en" imageUrl={(key) => url(key)} fit />

| Export | What | | --- | --- | | ResumeDocument | a resume in its template, one continuous A4 sheet | | ResumePaged | that sheet cut into A4 pages (fit to scale, print for the print route) | | TemplateThumb | a template's live thumbnail with sample content | | RESUME_TEMPLATES, templateSpec | the 100 template specs (traits, colour, font) | | paginate, breakLines | the engines, for tests and tools |

@thejob/resume-render/pro (no Svelte, no DOM, so Node can import it): proFeaturesUsed(layout, pages?) returns the billing feature keys a download needs (Pro template, Pro design, multi-page). The editors warn with it and resume-service's download gate enforces it, so the two cannot disagree. Free templates are FreeResumeTemplates in @thejob/schema.

@thejob/resume-render/docx exports a resume or cover letter as Word.

imageUrl(key) turns a stored photo key into a URL: each app knows its own image host.

Why it renders the same everywhere

linebreak.ts measures text with HarfBuzz (WebAssembly) over the TTFs in src/lib/fonts and writes every line break itself, pins text-sized boxes, and rounds line heights and spacing to whole pixels. resume-fonts.css and linebreak.ts both load the fonts from /fonts/resume/, so HarfBuzz reads exactly what the browser draws. Never swap the fonts for other copies.

Host app requirements:

  • Vite, with harfbuzzjs in optimizeDeps.exclude (it locates its .wasm next to its module).
  • This package's dist/fonts/*.ttf copied to the app's static/fonts/resume/. Bundler-resolved font URLs render on screen, but Chromium dropped every glyph from the printed PDF.

Full design notes: thejob-svelte-ui/docs/RESUME-BUILDER.md.

Develop

pnpm build    # svelte-package -> dist
pnpm check
pnpm yalc     # build + yalc publish --push to linked apps

yalc "pure" pushes do not refresh the copy pnpm resolves, so after a push copy dist into each app's readlink -f node_modules/@thejob/resume-render, then restart the app's dev server.

After any change to rendered output:

  1. Run the cross-browser gate: thejob-resume-service/.qa/xbrowser.mjs (Chromium, Firefox, WebKit; where every page starts must match across all three, 120/120 for the QA resumes in thejob-test1). WebKit does not run on this Fedora host: start a Playwright server container listening on ws://127.0.0.1:3333/ first. RES and TPL env vars narrow the run.
  2. Render real PDFs through resume-service (.qa/pdf.ts) in both apps and check they contain text (pdffonts lists fonts, pdftotext prints the name) and the page count matches the preview.
  3. Bump PDF_VERSION in resume-service src/repositories/resumes.ts.

Layout of the package

| File | What | | --- | --- | | src/lib/resume-document.svelte | the template: one component, template traits as classes | | src/lib/resume-templates.ts | the 100 template specs and their traits | | src/lib/resume-paged.svelte | lays the document out off-screen, paginates, shows pages through clipped windows; sets data-paginated when done | | src/lib/paginate.ts | where pages end (between blocks only, keep-with-next, widow/orphan rules) | | src/lib/linebreak.ts | HarfBuzz line breaking and box pinning over the bundled fonts | | src/lib/resume-format.ts | date and level formatting | | src/lib/resume-fonts.css | @font-face for Resume Sans/Serif/Mono at /fonts/resume/ | | src/lib/template-thumb.svelte | template gallery thumbnail | | src/lib/pro.ts | proFeaturesUsed: which Pro features a design uses (the ./pro entry) | | src/lib/fonts/ | the TTFs (shipped in dist/fonts) |

Labels and level names come in as props (labels, levels), so the package holds no app copy or i18n.