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

cardano-mercury-fork

v0.0.3-alpha

Published

Forked from Cardano Mercury Payments for Medusa JS

Readme

Cardano Mercury for Medusa JS

IMPORTANT: This software is still in an alpha developmental stage, please do not use it in production unless you're sure of what you're doing.

Installation Instructions

  1. Include the package in your project: npm i @cardano-mercury/medusajs
  2. Update your medusa-config.json file to add the following values:
    module.exports = defineConfig({
     projectConfig: {},
     plugins: [
         {
             resolve: "@cardano-mercury/medusajs",
             options: {
                 fixerApiKey: "d311e...aae3",
                 currencyFreaksApiKey: "87b3...d5a6",
                 oxrAppId: "24e5...6ecb",
                 xPubKey: "xpub1pc20...6ald",
             },
         },
     ],
     modules: [
         {
             resolve: "@medusajs/medusa/payment",
             options: {
                 providers: [
                     {
                         resolve: "@cardano-mercury/medusajs/providers/mercury",
                         options: {
                             fixerApiKey: "d311...aae3",
                             xPubKey: "xpub1pc20...6ald",
                             network: "preprod",
                             apiKey: "..."
                         }
                     }
                 ]
             }
         }
     ]})
    The most important of the variables for the plugin are the network, xPubKey (should be exported from your Eternl Wallet), and oxrAppId which can be acquired from Open Exchange Rates here: https://docs.openexchangerates.org/reference/api-introduction.
  3. Modify your .env environment variables to include the following:
    WALLET_EXTENDED_PUBLIC_KEY=xpub1pc20...6ald
    WALLET_NETWORK=preprod
    KOIOS_API_URL=https://preprod.koios.rest
    KOIOS_API_KEY=eyJh...VCJ9.eyJh...0oPw
    UPDATE_ADA_PRICE_PERIOD=15
    CHECK_ADA_PRICE_SCHEDULE="* * * * *"
    UPDATE_UNPAID_SESSIONS="*/2 * * * *"
    STALE_THRESHOLD_MINUTES=15
    UPDATE_UNPAID_SESSIONS="*/5 * * * *"
    All of these are required and should match the environment you are using.
  4. You will need to customize your frontend structure to correctly connect a Cardano light wallet from the user and craft and submit the transaction.

Known Issues

  • At the moment, the logic for updating currency conversion rates results in a large number of derived, child addresses being generated but never used when an order is left unpaid for a long time. This should be addressed to keep a single address attached to a single shopping cart in the future and allow for address reuse if never used while the order fully expires.