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

gudmed-trios

v1.0.0

Published

Shared MediEcho audio recording, digitization, and eRx processing for Gudmed portals

Readme

@gudmed/audio-erx

Standalone npm package for MediEcho audio features shared across Gudmed portals (Doctor, Patient, Admin, etc.).

Architecture

┌─────────────────────────────────────────────────────────────┐
│  @gudmed/audio-erx  (this package — publish once)           │
│  AudioInput · AudioDigitization · ProcessingPage · routes   │
└──────────────────────────┬──────────────────────────────────┘
                           │ imports
                           ▼
┌─────────────────────────────────────────────────────────────┐
│  @gudmed/audio-erx-bindings  (each portal provides this)    │
│  jwtAxios · Redux actions · ToasterMsg · constants          │
└─────────────────────────────────────────────────────────────┘

The package holds shared UI and logic. Each portal provides a bindings file that connects the package to that portal's API, Redux, and components.

Publish & update workflow

# 1. Change code in gudmed-audio-erx
cd gudmed-audio-erx
npm run build

# 2. Bump version (semver)
npm version patch   # 1.0.0 → 1.0.1 (bug fix)
# npm version minor # 1.0.0 → 1.1.0 (new feature)
# npm version major # 1.0.0 → 2.0.0 (breaking change)

# 3. Publish to your private registry
npm publish

# 4. In each portal — pull the new version
cd ../gudmed_doctorportal
npm update @gudmed/audio-erx
# or pin: npm install @gudmed/[email protected]

All portals that depend on @gudmed/audio-erx get the update after npm update and a rebuild/restart.

Local development (before publish)

Link the package from a sibling folder:

// portal package.json
"@gudmed/audio-erx": "file:../gudmed-audio-erx"
cd gudmed-audio-erx && npm install && npm run build
cd ../gudmed_doctorportal && npm install --legacy-peer-deps

After package changes: npm run build in gudmed-audio-erx, then restart the portal dev server.

Setup in a new portal

1. Install the package

npm install @gudmed/[email protected] --legacy-peer-deps

Or from local path during development:

"@gudmed/audio-erx": "file:../gudmed-audio-erx"

2. Create bindings

Copy bindings.example.jssrc/audioErxBindings/index.js and wire your portal's exports.
See Doctor Portal src/audioErxBindings/index.js for a full working example.

3. Vite config

import path from 'path';

export default defineConfig({
  resolve: {
    alias: {
      '@gudmed/audio-erx-bindings': path.resolve(
        __dirname,
        'src/audioErxBindings',
      ),
    },
    dedupe: ['react', 'react-dom'],
  },
  optimizeDeps: {
    include: ['@gudmed/audio-erx'],
  },
});

Do not alias @gudmed/audio-erx to source — resolve it from node_modules (built dist/).

4. Use in routes and components

import {
  AudioInput,
  AudioProcessConfig,
  audiodigitizationConfig,
} from '@gudmed/audio-erx';

// Routes (modules/index.jsx)
const routeConfigs = [
  ...AudioProcessConfig,
  ...audiodigitizationConfig,
];

// Component
<AudioInput opendialog={open} onDeny={setOpen} details={patientDetails} />

Publishing options

| Method | package.json | Best for | |--------|--------------|----------| | Private npm registry | "@gudmed/audio-erx": "^1.0.0" | Production teams | | GitHub Packages | Set publishConfig.registry | GitHub org | | Azure Artifacts | Org npm feed URL | Azure DevOps | | Local file | "file:../gudmed-audio-erx" | Local dev only | | Git URL | "git+https://github.com/org/gudmed-audio-erx.git#v1.0.1" | No registry |

GitHub Packages example

# .npmrc in gudmed-audio-erx and each portal
@gudmed:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=YOUR_TOKEN
// gudmed-audio-erx/package.json
"publishConfig": {
  "registry": "https://npm.pkg.github.com"
}

Exports

| Export | Description | |--------|-------------| | AudioInput | Record/upload audio dialog | | FileUploader | Drag-and-drop audio upload | | PatientBannerCard | Patient info banner in audio dialog | | AudioProcessConfig | Route config for /PresProcessingPage | | audiodigitizationConfig | Route config for /audiodigitization | | ProcessingPage | Full prescription processing screen | | AudioDigitization | Audio eRx pending list page | | CustomAudioPlayer | Multi-track audio player | | PdfViewer | eRx PDF preview/send dialog |

Versioning rules

  • patch — bug fixes, styling (1.0.0 → 1.0.1)
  • minor — new props, non-breaking features (1.0.0 → 1.1.0)
  • major — breaking bindings changes, removed exports (1.0.0 → 2.0.0)

If you add a new binding export that portals must provide, document it in bindings.example.js and bump minor or major.