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

@vimconnect/app-sdk

v0.4.58

Published

Vim Connect Application SDK — typed wrapper over coreSdk with collection-generated entity types

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

ayalabarzilayvimayalabarzilayvimasafdavasafdav

Keywords

vimehrhealthcaresdkvimconnect

Readme

@vimconnect/app-sdk

Typed SDK for building applications on the Vim Connect platform. Provides full IDE autocomplete, compile-time safety, and Zod schemas for runtime validation.

Installation

npm install @vimconnect/app-sdk

Requires Zod v4+ as a peer dependency.

Documentation

For the full SDK documentation — authentication, EHR reading/writing, Hub controls, React integration, error handling, and the complete API reference — see the Vim Connect Docs. AI-readable versions are also available at /llms.txt (index), /llms-full.txt (every page as markdown) and /collection/api-reference.json (generated entity types, events, context keys and method signatures — the reference tables are not in llms-full.txt).

Using with Claude Code

This package ships a skill — packaged as a plugin so it's ready for marketplace distribution later — that teaches Claude Code to look up the real SDK reference (llms.txt/llms-full.txt/collection/api-reference.json) instead of guessing entity fields, event ids, or method signatures. For now, add it to your project manually:

mkdir -p .claude/skills
cp -r node_modules/@vimconnect/app-sdk/skills/vim-app-sdk-docs .claude/skills/vim-app-sdk-docs

Where the types come from (maintainers)

These types are generated from the platform's official collection, not hand-written. The build pulls a specific published PROD collection version — pinned in collection-values.yaml — and generates generated/vim-types.ts from it. Types are always generated from the prod collection (no per-env split). That pin is types-only: bump it only when the type surface (entities / events / typeDefinitions / apiCatalog) changes. It is not the deployed collection that drives EHR behavior — that (the source of truth) lives in the backend and is inspected via connect-cli. See the repo CLAUDE.md "Collections, Types & the Source of Truth".

License

MIT