open-index/open-npm huggingface dataset:
npm package: @ovok/core
Description: [![npm version](https://badge.fury.io/js/@ovok%2Fcore.svg)](https://badge.fury.io/js/@ovok%2Fcore) [![Documentation](https://img.shields.io/badge/docs-sdk.ovok.com-blue)](https://sdk.ovok.com/)
Author: Fatih Kayan
Latest version: 0.2.51

# Ovok Core

[![npm version](https://badge.fury.io/js/@ovok%2Fcore.svg)](https://badge.fury.io/js/@ovok%2Fcore)
[![Documentation](https://img.shields.io/badge/docs-sdk.ovok.com-blue)](https://sdk.ovok.com/)

Core TypeScript SDK for healthcare applications. Provides authentication, AI-FHIR integration, observations, and healthcare data management.

## Features

- 🔐 Authentication & user management
- 🤖 AI-FHIR resources and planning
- 📊 Healthcare observations and measurements
- 💬 Chat AI integration
- 🤖 Bot execution framework
- 📋 Questionnaire responses

## Installation

```bash
npm install @ovok/core
# or
yarn add @ovok/core
# or
pnpm add @ovok/core
```

## Quick Start

```typescript
import { OvokClient } from "@ovok/core";

const client = new OvokClient({
  apiUrl: "your-api-url",
  // configuration
});
```

## Documentation

Full documentation and examples available at **[sdk.ovok.com](https://sdk.ovok.com/)**
npm package: @ovok/native
Description: React native component sdk for OVOK
Author: Fatih Kayan
Latest version: 0.3.14

# Ovok Mobile SDK

[![npm version](https://badge.fury.io/js/@ovok%2Fnative.svg)](https://badge.fury.io/js/@ovok%2Fnative)
[![Documentation](https://img.shields.io/badge/docs-sdk.ovok.com-blue)](https://sdk.ovok.com/)

A comprehensive React Native SDK for integrating Ovok-Core healthcare services into your mobile applications. Build powerful healthcare apps with pre-built components for authentication, device management, data synchronization, and more.

## ✨ Features

- 🔐 **Authentication & Security** - Complete auth flows with session management
- 📱 **Healthcare Components** - Pre-built UI components for medical data
- 🔄 **Data Synchronization** - Seamless sync with Apple Health & Android Health Connect
- 📋 **Questionnaire Forms** - Dynamic medical questionnaires and surveys
- 🩺 **Device Integration** - Bluetooth medical device connectivity
- 📊 **Progress Tracking** - Patient progress and measurement tracking
- 🎨 **Theming Support** - Customizable themes and styling
- 📖 **TypeScript Support** - Full type safety and IntelliSense

## 🚀 Quick Start

### Installation

```bash
npm install @ovok/native
# or
yarn add @ovok/native
```

## 📚 Documentation

Visit **[sdk.ovok.com](https://sdk.ovok.com/)** for:

- 📖 Complete API reference
- 🎯 Component examples
- 🏗️ Integration guides
- 💡 Best practices
- 🔧 Advanced configuration

## 📄 License

This project is licensed under the GNU 3.0 License - see the [LICENSE](LICENSE) file for details.
npm package: @ovos-media/coding-standard
Description: ovos-media coding standard
Author: ovos
Latest version: 3.0.1

## Install

```sh
# using npm
npm install --save-dev @ovos-media/coding-standard

# using yarn
yarn add --dev @ovos-media/coding-standard
```

## Usage

### `eslint.config.js`

```js
const eslint = require('@ovos-media/coding-standard/eslint');

module.exports = eslint();
```

The configuration is based on the recommended rulesets from [ESLint](https://eslint.org/) and [typescript-eslint](https://typescript-eslint.io/).

It also includes [ESLint Stylistic](https://eslint.style/) which replaces deprecated rules from eslint and typescript-eslint.

Currently, it uses ESLint v9 and typescript-eslint v8. (nodejs v18.18+ required)<br />
If you need to use this package on older nodejs, you can try the v2.x version, which is based on ESLint v8. (nodejs v16.10+ required)

`@ovos-media/coding-standard/eslint` exports a function that accepts an object with the following options:

- `console`: `ban`, `ban-log` or `allow` - whether to ban or allow console usage. Defaults to:
  - `ban-log` (which only allows `console.error()`, `console.warn()` and `console.info()`) when `react: true`,
  - `allow` otherwise.
- `disableTypeChecked`: List ts files which should be linted, but are not covered by `tsconfig.json`
  to avoid `Parsing error (...) TSConfig does not include this file`. [read more &raquo;](https://typescript-eslint.io/linting/troubleshooting/#i-get-errors-telling-me-eslint-was-configured-to-run--however-that-tsconfig-does-not--none-of-those-tsconfigs-include-this-file)
  Example: `['dangerfile.ts', '.storybook/*.ts?(x)']`
- `indent` (default: `2`): number of spaces to use for indentation or `tab` for tabs
- `testsDir` (default: `{spec,test,tests}`): directory where test files are located.
  Example: `src` for single directory, `{spec,tests}` to include multiple directories.
  In addition, files in `__tests__` folders and files with `*.spec.*`/`*.test.*` filenames are picked up as test files, even outside of `testsDir`.
- `cypress` (default: `false`): enable Cypress-specific rules
- `jest` (default: `false`): enable Jest-specific rules
- `mocha` (default: `false`): enable Mocha-specific rules
- `react` (default: `false`): enable React-specific rules
- `vitest` (default: `false`): enable Vitest-specific rules

The function returns an array of ESLint "[Flat Config](https://eslint.org/docs/v8.x/use/configure/configuration-files-new)" objects.
You may further customize the default configuration by adding your own configuration objects to the exported array.

```js
const eslint = require('@ovos-media/coding-standard/eslint');

module.exports = [
  ...eslint({ react: true, vitest: true }),
  // your custom config and overrides
  {
    ignores: ['public'],
  },
  {
    rules: {
      // toggle off unwanted rules
      'import/order': 'off',
    },
  },
  {
    files: ['**/*.?(m|c)[jt]s?(x)'],
    rules: {
      // your custom rules
    },
  },
];
```

---

### `prettier.config.js`

```js
module.exports = require('@ovos-media/coding-standard').prettier;
```
npm package: @ovos-media/play-live-realtime-ws-client
Description: This is a WebSocket browser-side client for ovos Play Live Realtime server.
Author: Krzysztof Gutkowski
Latest version: 1.1.1

# ovos Play Live Realtime WebSocket Client

This is a WebSocket browser-side client for ovos Play Live Realtime server.

The client is optimized for data transfer size, the package is compressed in high rate. It's suitable especially for mobile platform.

## Usage

### Establish connection to the server

```
realtime.init(params, callback);
```

Example with possible parameters:

```
realtime.init({
  host: host,
  port: port,
  user: {}, // optional, user defined json data
  handshakeCallback : function(data){} // optional, handshake callback function
}, function() {
  console.log('success');
});
```

### Send message with callback

```
realtime.request(route, msg, callback);
```

Example:

```
realtime.request("connector.entryHandler.ping", {
  foo: "bar"
}, function(response) {
  console.log(response);
});
```

### Send message without callback

```
realtime.notify(route, msg);
```

Example:

```
realtime.request("connector.entryHandler.ping", {
  foo: "bar"
});
```

### Receive message from the server

```
realtime.on(route, callback);
```

Example:

```
realtime.on('status.info', function(data) {
  console.log(data);
});
```

## Authors

* **NetEase, Inc.**

* **Krzysztof Gutkowski** - kg@ovos.at

## License

Copyright (c) 2012-2018 NetEase, Inc. and other contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
npm package: @ovos-media/react-realtime
Description: Official React bindings for Realtime
Author: Florentin
Latest version: 0.0.2

# React Realtime

Official React bindings for [Realtime](https://bitbucket.org/ovosdevs/lib-live-realtime-ws-client/src/master/).

## Installation

React Realtime requires **React 16 or later.**

```
npm install --save ovos-media/react-realtime
```

This assumes that you’re using [npm](http://npmjs.com/) package manager with a module bundler like [Webpack](https://webpack.js.org/) or [Browserify](http://browserify.org/) to consume [CommonJS modules](http://webpack.github.io/docs/commonjs.html).

## How Does It Work?

```
// App.js

import React, { Component } from 'react';

import { Provider as RealtimeProvider } from '@ovos-media/react-realtime';
import realtime from '@ovos-media/play-live-realtime-ws-client';

realtime.init({
	host: 'localhost',
	port: '3215',
	user: {}, // optional, user defined json data
	handshakeCallback : function(data){} // optional, handshake callback function
}, () => {
	console.log('success');
});


class App extends Component {
  render() {
    return (
			<RealtimeProvider realtime={realtime}>
				{children}
			</RealtimeProvider>
		);
	}
}

export default App;
```

```
// MyButton.js

import React, { Component } from 'react';

import { withRealtime } from '@ovos-media/react-realtime';


class MyButton extends Component {
  render() {
    return (
			<button onClick={this.pingRealtimeService}>
		);
	}

	pingRealtimeService = () => {
		const { realtime } = this.props;
		realtime.request("connector.entryHandler.ping", {
			foo: "bar"
		}, function(response) {
			console.log(response);
		});
	}
}

export default withRealtime()(MyButton);
```

## License

MIT
npm package: @ovos-media/simple-promise-queue
Description: A simple promise queue helper with concurrency settings.
Latest version: 1.0.12

[![npm (scoped)](https://img.shields.io/npm/v/@ovos-media/simple-promise-queue.svg)](https://www.npmjs.com/package/@ovos-media/simple-promise-queue)
[![Travis branch](https://img.shields.io/travis/ovos/js-helpers/master.svg)](https://travis-ci.org/ovos/js-helpers)
# simple-promise-queue

easily make your async functions queueable!

```js
import queueable from '@ovos-media/simple-promise-queue';

// just wrap your function to control execution sequence!
const queueableAsyncFunction = queueable(
  asyncFunction, 
  { concurrency: 1 }
);

// or as a decorator!
@queueable async function() {
  return request(...);
}
```

## Maintainers

[@flipace](https://github.com/flipace), [@unhawkable](https://github.com/unhawkable)

ovos media gmbh, [@ovos](https://github.com/ovos), [Visit us!](https://ovos.at)

## License

MIT
npm package: @ovos-media/ts-strictify
Description: Enable gradual TypeScript strict
Author: Christian Schröter
Latest version: 1.6.7

# ts-strictify

> Runs [TypeScript](hhttp://www.typescriptlang.org/) in strict mode on your changed files.

![Demo](./docs/assets/preview.png)

## Background

TBD

## How it works

When you start working on a new feature or fixing a bug, you will modify the code base in one way or another. `ts-strictify` will take a look at these changes - and only these changes (!) and will complain, if the files you have touched are not strict compliant.

That is different than TypeScript works. You could check a single file against the compiler, but the compiler would also look up the imports and the imports of the imports. Not exactly what you want, when you are looking for incrementally update path.

Head over to https://cschroeter.net/moving-to-strict-typescript/ for more insights.

## Install

With `yarn`:

```shellsession
yarn add --dev @ovos-media/ts-strictify
```

With `npm`:

```shellsession
npm install --save-dev @ovos-media/ts-strictify
```

## Usage

With `yarn`:

```shellsession
yarn ts-strictify
```

You can also disable a compiler flag, for example you want to disable `strictNullChecks`

```shellsession
yarn ts-strictify --strictNullChecks false
```

You can find a list of all available options [`here`](#options).

With [`npx`](https://npm.im/npx):

```shellsession
npx @ovos-media/ts-strictify
```

With `npm`:

1. Add `"ts-strictify": "ts-strictify"` to the scripts section of `package.json`.
2. `npm run ts-strictify`

## Pre-Commit Hook

You can run `ts-strictify` as a pre-commit hook using [`husky`](https://github.com/typicode/husky).

```shellstream
yarn add --dev husky
```

In `package.json`, add:

```
"husky": {
  "hooks": {
    "pre-commit": "ts-strictify"
  }
}
```

## Options

```bash
Options:
  --help                          Show help                       [boolean]
  --version                       Show version number             [boolean]
  --noImplicitAny                                 [boolean] [default: true]
  --noImplicitThis                                [boolean] [default: true]
  --alwaysStrict                                  [boolean] [default: true]
  --strictBindCallApply                           [boolean] [default: true]
  --strictNullChecks                              [boolean] [default: true]
  --strictFunctionTypes                           [boolean] [default: true]
  --strictPropertyInitialization                  [boolean] [default: true]
  --noUncheckedIndexedAccess                     [boolean] [default: false]
  --noEmit                                        [boolean] [default: true]
  --targetBranch                               [string] [default: "master"]
  --commitedFiles                                 [boolean] [default: true]
  --stagedFiles                                   [boolean] [default: true]
  --modifiedFiles                                 [boolean] [default: true]
  --untrackedFiles                                [boolean] [default: true]
  --createdFiles                                  [boolean] [default: true]
```

## Supported SCM

- Git
npm package: @ovos-media/tsconfig-to-swcconfig
Description: Convert tsconfig to swc config
Author: Songkeys
Latest version: 2.8.0-mod.0

# tsconfig-to-swcconfig

[![NPM version](https://img.shields.io/npm/v/tsconfig-to-swcconfig.svg?style=flat)](https://npmjs.org/package/tsconfig-to-swcconfig)
[![NPM downloads](https://img.shields.io/npm/dm/tsconfig-to-swcconfig.svg?style=flat)](https://npmjs.org/package/tsconfig-to-swcconfig)

Convert tsconfig to swc config.

> Why?
>
> (https://github.com/swc-project/swc/issues/1348)
>
> `swc` has no plans to support `tsconfig.json`, but it could be useful in some cases. For example, migrating from `tsc` to `swc` in a large project, you can use this tool to convert `tsconfig.json` to `.swcrc`, and then modify the `.swcrc` to make it work.

## Install

```bash
npm i tsconfig-to-swcconfig
```

## Usage

## Convert config in a tsconfig file

```typescript
import { convert } from 'tsconfig-to-swcconfig'

const swcConfig = convert() // will look for tsconfig under the cwd and convert it to swc config
```

Advanced options:

```typescript
import { convert } from 'tsconfig-to-swcconfig'

convert('tsconfig-filename.json', process.cwd(), {
  // more swc config to override...
  minify: true,
})
```

## Convert tsconfig value

Convert tsconfig value directly:

```typescript
import { convertTsConfig } from 'tsconfig-to-swcconfig'

const swcConfig = convertTsConfig({
  module: 'commonjs',
  target: 'es2018',
  strict: true,
  esModuleInterop: true,
})
```

Advanced usage:

```typescript
import { convertTsConfig } from 'tsconfig-to-swcconfig'

const swcConfig = convertTsConfig(
  { target: 'es2018' }, // tsconfig
  { minify: true }, // more swc config to override...
)
```

## CLI

To use the CLI, install globally:

```bash
npm i -g tsconfig-to-swcconfig
```

Then run:

```bash
tsconfig-to-swcconfig --help
```

```bash
Usage: tsconfig-to-swcconfig [options]
Alias: t2s [options]

Options:
  -f, --filename <filename>  filename to tsconfig (default: "tsconfig.json")
  -c, --cwd <cwd>            cwd (default: process.cwd())
  -o, --output <output>      output file (default: stdout)
  -s, --set <name>=<value>   set additional swcrc options
  -h, --help                 display help for command
```

Instead of installing globally, you can also use `npx` to run the CLI without installing:

```bash
npx tsconfig-to-swcconfig -f tsconfig.json -c /path/to/project -o swc.config.js
```

## License

MIT
npm package: @ovos-media/vite-plugins
Description: A set of vite plugins, developed by ovos media gmbh.
Author: ovos media gmbh
Latest version: 3.0.1

# ovos vite plugins

This package contains a few custom vite plugins used by ovos media.

The `graphql` and `po2json` plugins may be useful for other projects as well.

The source is not yet publicly available on github, only the published package on npm.

## Usage

```ts
  import { graphql, po2json } from '@ovos-media/vite-plugins';

  // add the plugins to your vite config
  const viteConfig = {
    plugins: [
      graphql,
      po2json(),
    ]
  };
```

## Development

```sh
# in the vite-plugins folder
yarn link

# in the folder where you want to use the package
yarn link "@ovos-media/vite-plugins"

# in the vite-plugins folder
yarn watch # this will "build" the declaration files and move the to src code to `dist`, which will be published on npm

# release a new version
# first update the version in package.json and then
npm publish
```

## License
MIT