open-index/open-npm huggingface dataset:
npm package: @svsharma/npmstarterpack
Description: Generates a random number between a specified range
Latest version: 2.0.0

# @svsharma/npmstarterpack

[![npm (scoped)](https://img.shields.io/badge/NPM%20Starter%20Pack-JS%20Starter%20Pack-green)](https://www.npmjs.com/package/@svsharma/npmstarterpack)
[![GitHub issues](https://img.shields.io/github/issues/sriramvsharma/npmstarterpack)](https://github.com/sriramvsharma/npmstarterpack/issues)

NPM Starter Pack
npm package: @svssdeva/video-data-bridge
Description: Capacitor plugin for passing data from web to android for native video player
Author: Deveshwar Jaiswal
Latest version: 1.0.0

# @svssdeva/video-data-bridge

Capacitor plugin for passing data from web to android

## Install

```bash
npm install @svssdeva/video-data-bridge
npx cap sync
```

## API

<docgen-index>

* [`openVideo(...)`](#openvideo)
* [`openDownloadsPage()`](#opendownloadspage)
* [Interfaces](#interfaces)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### openVideo(...)

```typescript
openVideo(videoData: VideoData) => Promise<{ success: boolean; }>
```

| Param           | Type                                            |
| --------------- | ----------------------------------------------- |
| **`videoData`** | <code><a href="#videodata">VideoData</a></code> |

**Returns:** <code>Promise&lt;{ success: boolean; }&gt;</code>

--------------------


### openDownloadsPage()

```typescript
openDownloadsPage() => Promise<{ success: boolean; }>
```

**Returns:** <code>Promise&lt;{ success: boolean; }&gt;</code>

--------------------


### Interfaces


#### VideoData

| Prop             | Type                |
| ---------------- | ------------------- |
| **`token`**      | <code>string</code> |
| **`userId`**     | <code>string</code> |
| **`videoData`**  | <code>string</code> |
| **`clientId`**   | <code>string</code> |
| **`clientType`** | <code>string</code> |
| **`randomId`**   | <code>string</code> |

</docgen-api>
npm package: @svsticky/content
Description: Type definitions for content types provided by Sticky's content management system.
Author: Job Vonk
Latest version: 1.0.6

# @svsticky/content

Type definitions for content types provided by Sticky's content management system.
This package makes it easier for other JS projects to retrieve content from the CMS, especially in combination with
Payload's sdk library, as illustrated below. The type definitions in this package allow for auto-completions
in your editor and type-checking for field types and slugs for all the content entities that the CMS exposes.

```ts
import { PayloadSDK } from "@payloadcms/sdk";
import type { Config } from "@svsticky/content";

const sdk = new PayloadSDK<Config>({
  baseURL: "https://content.svsticky.com/api", // Whatever the url is to the CMS...
})
```
npm package: @svta.org/common-media-library
Description: > **Warning** > This library has moved to a new org! The NPM org has changed from `svta.org` to `svta` Please use [@svta/common-media-library](https://github.com/streaming-video-technology-alliance/common-media-library). This org will be deleted in the fu
Latest version: 0.4.1


> **Warning**
> This library has moved to a new org! The NPM org has changed from `svta.org` to `svta` Please use [@svta/common-media-library](https://github.com/streaming-video-technology-alliance/common-media-library). This org will be deleted in the future.

# common-media-library
A common library for media playback in JavaScript

Looking at open source players like [hls.js](https://github.com/video-dev/hls.js/), [dash.js](https://github.com/Dash-Industry-Forum/dash.js/) and [shaka-player](https://github.com/shaka-project/shaka-player) there are common pieces of functionality that have been implemented independently, and sometimes copy and pasted, across the libraries. This is particularly true when looking at standards based features, like ID3 parsing, 608 parsing and CMCD. Since the functionality is shared in spirit but not implementation, they can fall out of sync where certain bugs are fixed in one player but not the others. The goal of this library is to create a single place where these utilities can be maintained and distributed.

## Project structure
This project is a mono-repo with the following workspaces: `lib`, `docs`. The `lib` package contains the compiled code for the library which is published to npm. The `docs` package contains the documentation for the library and is published to GitHub pages.

## Installation
```bash
npm install @svta.org/common-media-library
```

## Usage
Too ensure the smallest bundle sizes possible, it is best practice to import all members and type definitions
individually from the library.
```typescript
import { appendCmcdQuery } from '@svta.org/common-media-library/cmcd/appendCmcdQuery';
import { CmcdObjectType } from '@svta.org/common-media-library/cmcd/CmcdObjectType';

const cmcd = {
	sid: '4f2867f2-b0fd-4db7-a3e0-cea7dff44cfb',
	cid: 'cc002fc3-d9e1-418d-9a5f-3d0eac601882',
	d: 324.69,
	ot: CmcdObjectType.MANIFEST,
	['com.example-hello']: 'world',
};

const cmcdUrl = appendCmcdQuery(cmcd, 'https://example.com/playlist.m3u8');
console.log(cmcdUrl);
// https://example.com/playlist.m3u8?CMCD=cid%3D%22cc002fc3-d9e1-418d-9a5f-3d0eac601882%22%2Ccom.example-hello%3D%22world%22%2Cd%3D325%2Cot%3Dm%2Csid%3D%224f2867f2-b0fd-4db7-a3e0-cea7dff44cfb%22
```

If bundle size isn't a concern, all members and type definitions can also be imported from the root of the library, or from the feature namespace.
```typescript
import { appendCmcdQuery, CmcdObjectType } from '@svta.org/common-media-library';
```
```typescript
import { appendCmcdQuery, CmcdObjectType } from '@svta.org/common-media-library/cmcd';
```

## Documentation
API docs can be found [here](https://streaming-video-technology-alliance.github.io/common-media-library/).