open-index/open-npm huggingface dataset:
npm package: @rackspace-identity-platform/cookie-monster
Description: Tools for managing browser sessions for individual tabs
Author: Timothy Farrell
Latest version: 0.5.0

# Cookie Monster

Cookie Monster is a set of tools to manage tab-based session cookies.

The process for tab-based sessions is to use browser cookies for transport rather than an data storage. CookieMonster provides two tools help make this happen, a script and a page template. The script will hook into all server-communication methods in the browser to create this affect. The page template is designed as a customizable HTML page to serve in case the server endpoint receives an webpage GET request with no session cookie. It checks for a session and resends the request or forwards the browser to a provided auth url.

## Implementation Prerequisites

- The CookieMonster script must be loaded (synchronously) after polyfills but before any code that might wrap fetch/XHR (if those features are used).
- Session cookies must have "httpOnly" turned off.

## Usage

Add CookieMonster to your project:

Using npm:

```
npm install --save @rackspace-identity-platform/cookie-monster
```

Or yarn:

```
yarn add @rackspace-identity-platform/cookie-monster
```

See each feature's documentation linked below.

- [Using the cookieMonster script](./docs/script.md)
- [Using the loading template](./docs/template.md)


## TODO

- Consider timeouts on `sessionStorage` values.
- Add semaphors to mitigate race conditions that may happen when more than one tab sends requests to the server at a time.
npm package: @racksync/node-red-contrib-hass-flow
Description: Make you Home Assistant instance easier to implement by all these extension node
Author: RACKSYNC CO., LTD.
Latest version: 1.0.6

# HASS Flow is Node-RED Module for Home Assistant

[![Platform](https://img.shields.io/badge/platform-Node--RED-red)](https://nodered.org)
[![node-red-contrib-hass-flow](https://img.shields.io/github/v/release/racksync/node-red-contrib-hass-flow)](https://github.com/racksync/node-red-contrib-hass-flow/releases) [![last commit](https://img.shields.io/github/last-commit/racksync/node-red-contrib-hass-flow)](https://github.com/racksync/node-red-contrib-hass-flow/commit/)

# Installation

You can install the nodes using "Manage palette" from node-red kebab menu or run the following command in the root directory of your Node-RED installation

```
npm install node-red-contrib-hass-flow --save
```

# Usage

Put "Toggle" entity from input_boolean into input together with base flow, Now you can easier toggle from Home Assistant UI then.

![racksync-screenshot](https://github.com/racksync/node-red-contrib-hass-flow/blob/main/images/screenshot.png?raw=true)

### Node-RED Node by RACKSYNC
- [flows](https://flows.nodered.org/node/@racksync/node-red-contrib-hass-flow)
- [Tradfri Remote](https://flows.nodered.org/node/@racksync/node-red-contrib-hass-tradfri-remote)

![racksync-node](https://github.com/racksync/node-red-contrib-hass-tradfri-remote/blob/main/images/nodes.png?raw=true)

### Tips

- It is recommended to always do a full deploy when you changed some of the nodes of this library to prevent unexpected behavior.
- Always use debug node to test message payload before using in Production.

### Automation Training

- [Product & Services](http://racksync.com)
- [Training & Course](https://facebook.com/racksync)

## [RACKSYNC CO., LTD.](https://racksync.com)

We helps our customers to create life easier across the border of entire technology stack with household and business solutions. We modernize life with Information Technology, Optimize and collect data to make everything possible, secure & trusty
\
\
RACKSYNC COMPANY LIMITED \
Suratthani, Thailand \
Email : devops@racksync.com \
Tel : +66 85 880 8885 

[![Home Automation Thailand Discord](https://img.shields.io/discord/986181205504438345?style=for-the-badge)](https://discord.gg/Wc5CwnWkp4) [![Github](https://img.shields.io/github/followers/racksync?style=for-the-badge)](https://github.com/racksync) 
[![WebsiteStatus](https://img.shields.io/website?down_color=grey&down_message=Offline&style=for-the-badge&up_color=green&up_message=Online&url=https%3A%2F%2Fracksync.com)](https://racksync.com)
npm package: @raconteur-media/design-tokens
Description: A package to distrubbute Raconteur Media designn tokens
Author: Nicola Pernice
Latest version: 1.0.9

# Raconteur Design Tokens

Raconteur Media Ltd Design Tokens.

## Installation

`$ npm install @raconteur-media/desing-tokens`

Or add this package to your `package.json` file:

```
"dependencies": {
    "@raconteur-media/desing-tokens": "1.0.3"
  }
```

## Content

```
.
├── CHANGELOG.md
├── README.md
├── dist
│   ├── index.cjs               // Theme UI Raconteur Design Tokens in CommonJS format
│   ├── index.css               // Theme UI Raconteur Design Tokens as CSS variables 
│   ├── index.js                // Theme UI Raconteur Design Tokens in ES format (entry point copy of raconteur-theme.js)
│   ├── index.json              // Theme UI Raconteur Design Tokens in JSON format 
│   ├── index.scss              // Theme UI Raconteur Design Tokens as SASS variables
│   ├── rac-dsm-theme.cjs       // DSM Raconteur Design Tokens in CommonJS format
│   ├── rac-dsm-theme.js        // DSM Raconteur Design Tokens in ES format
│   ├── rac-dsm-theme.json      // DSM Raconteur Design Tokens in JSON format
│   └── rac-dsm-theme.scss      // DSM Raconteur Design Tokens in SASS format
├── package.json
├── scripts
│   ├── js-to-scss.js
│   ├── json-to-css-variables.js
│   ├── theme-to-custom-properties.js
│   └── theme-to-json.js
├── src
│   ├── raconteur-theme.js      // Theme UI Raconteur Design Tokens
│   └── style-data.json         // DSM Design Tokens
```

### Build

#### Theme UI

Any update shoudl occur in `src/raconteur-theme.js` To generate any other variation just run `yarn theme`

#### DSM

To get InVision DSM tokens and generate any other variation just run `yarn dsm`

### Script

`yarn dsm` To update tokens based on InVision DSM

`yarn theme` To update tokens based on Theme UI

### Refs

-   [Js to SCSS](https://github.com/MakhBeth/js-to-scss#readme)
-   [JSON to CSS Variables](https://github.com/tcarlsen/json-to-css-variables#readme)

### TO DO

- [ ] Get InVision DSM tokens in a Theme UI Format to achive an autoated design/dev sync.
- [ ] Add more refs.
npm package: @racsys/eslint-config
Description: ESLint configuration used by RAC
Latest version: 1.5.0

# RAC ESLint config

## Setup

1. Install the dependencies
```
npm i -D eslint @racsys/eslint-config
```

2. Create a `.eslintrc.json` file extending the config:
```
{
  "extends": "@racsys/eslint-config/react"
  // "extends": "@racsys/eslint-config/node"
}
```

> You can also use a `.eslintrc.js` instead of JSON if you prefer.
npm package: @racunko/react-native-sms
Description: A react native android module to retrieve sms from inbox
Author: Dragan Cabarkapa
Latest version: 1.0.1


# react-native-sms

Note: Limited functionality not appropriate for production use.

## Getting started

`$ yarn add @racunko/react-native-sms`

### Mostly automatic installation

`$ react-native link react-native-sms`

### Manual installation

#### Android

1. Open up `android/app/src/main/java/[...]/MainActivity.java`
  - Add `import com.racunko.rn.SmsPackage;` to the imports at the top of the file
  - Add `new SmsPackage()` to the list returned by the `getPackages()` method
2. Append the following lines to `android/settings.gradle`:
    ```
    include ':react-native-sms'
    project(':react-native-sms').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-sms/android')
    ```
3. Insert the following lines inside the dependencies block in `android/app/build.gradle`:
    ```
      compile project(':react-native-sms')
    ```

## Usage
- Retrieve all SMS messages

```javascript
import Sms from '@racunko/react-native-sms';

const filter = {
  box: 'inbox', // 'inbox' (default), 'sent', 'draft', 'outbox', 'failed', 'queued', and '' for all
};

const failCallback = error => {
  console.log('error: ' + error);
};

const successCallback = (smsCount, smsList) => {
  let messages = JSON.parse(smsList);
  for (let message of messages) {
    console.log(`id: ${message._id}, date: ${message.date}, address: ${message.address}, body: ${message.body}`);
  }
};

Sms.list(JSON.stringify(filter), successCallback, failCallback);

/* 
Each sms will be represents by a JSON object represented below

{
  "_id": 1234,
  "thread_id": 3,
  "address": "2900",
  "person": -1,
  "date": 1365053816196,
  "date_sent": 0,
  "protocol": 0,
  "read": 1,
  "status": -1,
  "type": 1,
  "body": "Hello There, I am an SMS",
  "service_center": "+60162999922",
  "locked": 0,
  "error_code": -1,
  "sub_id": -1,
  "seen": 1,
  "deletable": 0,
  "sim_slot": 0,
  "hidden": 0,
  "app_id": 0,
  "msg_id": 0,
  "reserved": 0,
  "pri": 0,
  "teleservice_id": 0,
  "svc_cmd": 0,
  "roam_pending": 0,
  "spam_report": 0,
  "secret_mode": 0,
  "safe_message": 0,
  "favorite": 0
}
*/
```
npm package: @racy/azure-middleware
Description: racy implementation for azure middleware inspired on Middy
Author: Diego A. Zapata Häntsch
Latest version: 1.1.9

# @racy/azure-middleware

It is a middleware implementation for azure functions inspired on MiddyJs.

It works in the same way as MiddyJs but without plugins.

## Installation

```sh
npm install @racy/azure-middleware --save
```

## Example

```typescript
import {AzureMiddleware} from '@racy/azure-middleware'

const middlware = new AzureMiddleware(handler); // where handler is you azure function;
middleware.use(yourMiddlewareBuilder()); // the middleware builder function should return a MiddlewareConfiguration object

export = middleware.listen(); // this should return the final handler your original handler should be wrapped
                             // in the middleware onion patter in the same way that middy works;
```
npm package: @radai/hl7-checker
Description: HL7 message validation and checking library
Latest version: 0.1.5

# HL7 Checker

A TypeScript-based HL7 message validator that checks segments, fields, and components based on configurable validation rules.

Supports message types like ORM_O01, ORU_R01, and ADT_A01, with extensible rules defined in a JSON config file.

## Features

Validates HL7 v2 messages using @medplum/core

Rules defined externally via JSON (field, component, required, etc.)

Differentiates validation based on message type (e.g., ORM_O01 vs ORU_R01)

Modular and extensible rule system

## Installation

```bash
npm install @radai/hl7-checker
```

## Configuration

Rules are defined in a JSON file. The structure supports message-type-specific validation:

```json
{
  "ORM_O01": {
    "MSH": [
      {
        "field": 9,
        "required": true,
        "components": [
          {
            "component": 1,
            "required": true
          },
          {
            "component": 2,
            "required": true
          }
        ]
      }
    ],
    "PID": [
      {
        "field": 3,
        "required": true
      }
    ]
  }
}
```

Each top-level key is a combined message type and trigger event (<MSGTYPE>\_<EVENT>), such as ORM_O01, ORU_R01, etc.

## Usage

```ts
import { HL7Validator } from "@your-org/hl7-validator";

const validator = new HL7Validator("./rules.json");

const message = "MSH|...";

const result = validator.validate(message);
```

## Output

The result includes:

- segments: Array of segments with field validation statuses
- messages: General validation messages (e.g., parse failures)
- encoding: Separators and control characters extracted from the HL7 message

Example:

```json
{
  "segments": [
    {
      "name": "MSH",
      "fields": [
        {
          "name": "MSH.9",
          "validationResult": {
            "status": "error",
            "messages": ["MSH.9.2: Missing required component"]
          }
        }
      ]
    }
  ],
  "messages": [],
  "encoding": {
    "segmentSeparator": "\r",
    "fieldSeparator": "|",
    "componentSeparator": "^",
    ...
  }
}
```

## License

MIT