BUILD / MEDUSAJS PLUGINS

MedusaJS plugins, extracted from live builds.

Five MIT-licensed MedusaJS v2 plugins. Source on GitHub. Not a theme shop catalogue — each one was cut out of a working commerce stack.

Discuss a MedusaJS build ↗MedusaJS agency ↗
01

THE PUBLIC CATALOG

GITHUB / MIT / MEDUSAJS V2

Hollow Point publishes MedusaJS plugins as separate repositories, not as a mega-package. GitHub is where you read the source. The four utility plugins still install from the @hollowpoint-io npm scope; staff permissions currently installs from its tagged GitHub release. A GitHub source archive is not an install path.

These are not a substitute for a MedusaJS build. They are the pieces that made that build possible, published so a merchant or another developer can inspect the work before talking to us.

01 / REDIRECTS

GitHub ↗

URL redirects

@hollowpoint-io/medusa-plugin-redirects

The redirects store of truth MedusaJS core does not have.

Admin CRUD, bulk import, Shopify-style provenance, and a store endpoint so the storefront can cache the full set at the edge instead of hitting the database on every request.

  • Admin URL Redirects
  • Bulk import
  • Store lookup / full set

npm install @hollowpoint-io/medusa-plugin-redirects

02 / MEDIA

GitHub ↗

Media library

@hollowpoint-io/medusa-plugin-media-library

A browsable record of every upload the File Module leaves untracked.

Filter, upload via the host File Module, copy URL, edit alt and role. Deleting a library row never deletes the stored file, so existing references keep working.

  • Admin Media Library
  • URL-keyed registry
  • Registry-only deletes

npm install @hollowpoint-io/medusa-plugin-media-library

03 / NAVIGATION

GitHub ↗

Navigation menus

@hollowpoint-io/medusa-plugin-navigation

Menus with Shopify link-list parity, instead of hardcoding them.

Named menus identified by handle, nested items, and types for collection, category, product, page, blog, URL and header. The storefront fetches a tree.

  • Admin menus
  • Nested tree API
  • Header / footer / legal

npm install @hollowpoint-io/medusa-plugin-navigation

04 / KLAVIYO

GitHub ↗

Klaviyo

@hollowpoint-io/medusa-plugin-klaviyo

Consent-first Started Checkout and Placed Order events.

Idempotent cart and order events, consent sync for migrated stores, and a honeypot newsletter subscribe route. An unconfigured install no-ops instead of throwing.

  • Started Checkout
  • Placed Order
  • Subscribe + consent

npm install @hollowpoint-io/medusa-plugin-klaviyo

05 / RBAC

GitHub ↗Release ↗

Staff permissions

@hollowpoint-io/medusa-plugin-staff-permissions

Server-enforced View/Manage grants. Core MedusaJS keeps this for Enterprise.

Eight business areas, immutable recovery owners, an atomic audit trail and a fail-closed route inventory. User metadata and JWT claims never grant access.

  • Admin staff permissions
  • Route inventory
  • Audit trail

Install the v0.1.0 GitHub release tarball (npm listing to follow).

02

HOW TO USE THEM

SOURCE ON GITHUB / ARTIFACT SEPARATE

SOURCE

GitHub is for reading the code.

Each repository is public, MIT, and kept free of client names and credentials. Use it to audit behaviour, file an issue, or decide whether the plugin matches the gap in your stack.

INSTALL

Do not install from a git URL.

MedusaJS plugins ship a compiled payload. A GitHub archive does not contain it, so npm install github:hollowpoint-io/… will not load as a plugin. Use the npm package name, or the release tarball for staff permissions.

03

WHAT IS NOT ON THIS PAGE

NOT A DUMP / STARTER STAYS PRIVATE

Further packages ship when a client build leaves behind something that can stand alone with a clean-host install. Payments, warehouse connectors and the Shopify import kit are not listed here. The delivery starter stays private; its parts become public, not the whole machine.

If you need the operating stack around these plugins — migration, payments, Admin, storefront — that is the MedusaJS agency conversation, not a plugin install.

04

FREQUENTLY ASKED QUESTIONS

PLAIN ANSWERS / MEDUSAJS PLUGINS
01 / FAQ

What MedusaJS plugins does Hollow Point publish?

Five open-source MedusaJS v2 plugins: URL redirects, media library, navigation menus, Klaviyo, and staff permissions. Each is MIT-licensed, extracted from a live commerce build, and published as its own GitHub repository under hollowpoint-io.

02 / FAQ

How do I install Hollow Point MedusaJS plugins?

Read the source on GitHub. Install redirects, media library, navigation and Klaviyo with npm using the @hollowpoint-io package name. Staff permissions currently ships as the tagged GitHub release tarball. Do not npm-install the GitHub repo URL: GitHub source archives do not contain the compiled plugin payload.

03 / FAQ

Are these official Medusa packages?

No. They are third-party MIT packages maintained by Hollow Point, an official Medusa Expert. They are not Medusa core and they are not a performance guarantee.

04 / FAQ

Can I install the plugins directly from GitHub?

Use GitHub to read and audit the source. Do not install from a GitHub archive or github: specifier. The published artifact is a built package; a raw clone does not load as a MedusaJS plugin.

05 / FAQ

Will more MedusaJS integrations be published?

Yes, when a client build leaves behind a package that can stand alone. The delivery starter stays private. Packages that still need a production proof, such as payments and warehouse connectors, are not listed here until that gate is met.