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

@test-publish-sdks/di-sdk

v0.0.24

Published

Extensibility SDK interface for building platform extensions - Part of Candescent Developer Experience (CDX)

Readme

@cdx-extensions/di-sdk

Part of the Candescent Developer Experience (CDX)

Core SDK interface for building platform extensions. This package provides the unified PlatformSDK and does not depend on @cdx-extensions/di-sdk-web or @cdx-extensions/di-sdk-mobile. The host app installs only the platform it needs and registers it with the SDK (dependency injection). That avoids bundlers like Metro resolving both platform packages when the app uses only one.

This library is independent. Dependencies are resolved from JFrog when you run npm install in this folder. Build and publish from this directory.

Installation

Install the core SDK and only the platform you need (web or mobile).

Web:

npm install @cdx-extensions/di-sdk @cdx-extensions/di-sdk-web

Mobile (e.g. React Native):

npm install @cdx-extensions/di-sdk @cdx-extensions/di-sdk-mobile

Quick Start

The host app (the one that has di-sdk-web or di-sdk-mobile) calls PlatformSDK.init({ platform }) once at bootstrap. Widgets and extensions only call PlatformSDK.getInstance() with no arguments. getInstance() throws if the host never called init().

Host app (bootstrap)

Only the host app should call init(). Do this once at app entry (e.g. root component or main), before any widget runs.

Web host:

import { PlatformSDK } from '@cdx-extensions/di-sdk';
import { WebPlatform } from '@cdx-extensions/di-sdk-web';

// Once at bootstrap
PlatformSDK.init({ platform: WebPlatform.getInstance() });

Mobile host (e.g. React Native):

import { PlatformSDK } from '@cdx-extensions/di-sdk';
import { MobilePlatform } from '@cdx-extensions/di-sdk-mobile';

// Once at bootstrap
PlatformSDK.init({ platform: MobilePlatform.getInstance() });

Widget / extension

Widgets depend only on @cdx-extensions/di-sdk. They must run inside a host that has already called PlatformSDK.init().

import { PlatformSDK } from '@cdx-extensions/di-sdk';

const sdk = PlatformSDK.getInstance();
const userContext = sdk.useUserContext();
const httpClient = sdk.getHttpClient();

Because the core SDK never imports di-sdk-web or di-sdk-mobile, a mobile-only app does not need the web package installed and Metro will not try to resolve it.

For a full description of the approach, flow, and diagrams, see PLATFORM_REGISTRATION.md.

Development

From the repository root:

cd libs/common/extensibility-sdk
npm install
npm run build

To publish (e.g. after merging to main):

npm run build
npm publish

Publishing under development: To publish this lib while it is under development without affecting the main version, run from this directory: npm publish --tag development.

Documentation

License

ISC

CDX = Candescent Developer Experience