Published Packages
A ruled list of maintained npm packages, each row with the name, version, license, weekly downloads, a short description, and an install command.
A ruled list of maintained npm packages, each row with the name, version, license, weekly downloads, a short description, and an install command.
Search blocks by description or jump to a page.
The source for every Portfolio block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Published Packages is a bordered list of four npm libraries rendered as ruled rows. Each row leads with the package name in mono, a version chip, and the license, then a right-aligned weekly download figure beside a small download icon. Under that sits a one line description and a muted install command strip in mono with a copy icon. A link to the full npm profile closes the section.
Packages is a typed array with name, version, license, downloads, description, and install fields, so a real registry profile drops in without touching markup. The version chip and install strip reuse the muted chip and code treatments, which keeps the row reading as package metadata rather than a marketing card. The copy and download icons are static affordances, not wired handlers.
Reach for this block on a developer portfolio when published libraries are a meaningful part of the record, and a plain project list would hide the download numbers that prove reach. The installer replaces the four package objects with their own, keeping the description to one honest line about what each library actually does.
A natural flow around it on a Portfolio Pro page:
Before
After
One strong use is the maintained npm library list. Other package layouts:
Tip: lead with the weekly download figure only when it is genuinely strong; for newer packages, let the description and a clean install command carry the row.