open-index/open-npm huggingface dataset:
npm package: @hex0b1t/palindrome
Description: A simple palindrome checker
Latest version: 2.0.0

# @hex0b1t/palindrome-checker

A simple palindrome checker function. 
Using this package is easy

run npm install @hex0b1t/palindrome-checker

add the package to your script

Call the palindrome function with a word as an argument and it will tell if the word is a palindrome or not
npm package: @hex0b1t/palindrome-checker
Description: A simple palindrome checker
Latest version: 2.0.0

# @hex0b1t/palindrome-checker

A simple palindrome checker function. 
Using this package is easy

run npm install @hex0b1t/palindrome-checker

add the package to your script

Call the palindrome function with a word as an argument and it will tell if the word is a palindrome or not
npm package: @hex2r/react-announcer
Description: Accessible announcer component for React apps using the Context API.   Renders live-region messages for screen readers and provides a simple hook for dispatching announcements from anywhere in your component tree.
Latest version: 0.1.2

# react-announcer

Accessible announcer component for React apps using the Context API.  
Renders live-region messages for screen readers and provides a simple hook for dispatching announcements from anywhere in your component tree.

> 🔊 Perfect for accessibility-friendly UIs, form feedback, status updates, or dynamic ARIA alerts.

This package simplifies the process of announcing messages to screen readers by:

- Managing announcements via React Context

- Offering a default AnnouncementRegion component (screen reader only)

- Allowing you to create your own custom rendering of announcements

- Supporting both polite and assertive modes for Screen Readers

<br />

## 📦 Installation

**npm:**

```bash
npm install --save-dev @hex2r/react-announcer
```

**pnpm:**

```bash
pnpm install --save-dev @hex2r/react-announcer
```

**yarn:**

```bash
yarn add -D @hex2r/react-announcer
```

### Peer Dependencies

`react version ^18.3.0`
<br />

### Usage in your components

Do it easy using `useAnnouncer()` hook

```jsx
const { announce } = useAnnouncer()

...
const handleClick = () => {
  announce({ message: "Assertive hello from demo!", assertive: true })
}
...
```

### 📦 API Reference

<br />

`<AnnouncerProvider>`

Wraps your app and provides announcements state and dispatch function via context.

```jsx
<AnnouncerProvider>
  {(announcements) => (
    <>
      <AnnouncementRegion announcements={announcements} />
      {/* ... */}
    </>
  )}
</AnnouncerProvider>
```

<br />

`useAnnouncer() hook`

Hook to dispatch announcements.

```jsx
const { announce } = useAnnouncer()
announce({ message: "User created", assertive: false })
```

<br />

`AnnouncementRegion`

Component that renders screen-reader accessible messages

| Prop              | Type             | Default | Description                                                        |
| ----------------- | ---------------- | ------- | ------------------------------------------------------------------ |
| `announcements`   | `Announcement[]` | —       | List of current announcements                                      |
| `srOnlySupported` | `boolean`        | `false` | Use `className="sr-only"` instead of inline visually hidden styles |
| `stackLimit`      | `number`         | `4`     | Number of last announcements to display                            |

<br />

```jsx
<AnnouncementRegion
  announcements={announcements}
  srOnlySupported
  stackLimit={3}
/>
```

<br />

### ♿ Accessibility Notes

The `AnnouncementRegion` component ensures that assistive technology is notified of updates using `aria-live` and appropriate roles (`status` for `polite`, `alert` for `assertive`).

If you're using Tailwind or already have an `.sr-only` class, you can pass `srOnlySupported={true}` to avoid inline styles.

Supports announcing multiple messages with `stackLimit`.
npm package: @hexa-ai/node-red-contrib-hexa-ai
Description: A set of nodes for working with variables (reading, writing, history, alarm).
Author: Hexa-AI
Latest version: 1.1.1

# node-red-contrib-hexa-ai

[![platform](https://img.shields.io/badge/platform-Node--RED-red)](https://nodered.org)
![NPM version](https://badge.fury.io/js/@hexa-ai%2Fnode-red-contrib-hexa-ai.svg)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

This package provides a set of nodes in Node-RED to manage variables data, history (using [warp10](https://www.warp10.io/)) and alarms.

## Pre-requisites

The package requires [Node-RED](https://nodered.org) to be installed.

## Install

To install the stable version use the `Menu - Manage palette` option and search for `node-red-contrib-hexa-ai`, or run the following command in your Node-RED user directory - typically `~/.node-red`:

    npm i node-red-contrib-hexa-ai

Restart your Node-RED instance and you should have the nodes available in the palette and a new `Hexa AI` tab in the right side panel.

## Available nodes

* :arrow_heading_down: **write-variable** : A node for storing typed variables
  * Variable value stored in node-red global context
  * Js primitive type and user-friendly unit for display
  * Data historicization (with warp10)
  * Value monitoring and alert trigger
* :arrow_heading_up: **read-variable** : A node for receiving values from write variable
  * Value is sent at the initialization of the node (using global context)
  * Value modification sent in real time using event bus
* :bell: **on-alarm** : A node for receiving alarms triggered by write variable
  * Two outputs : when an alarm is up, when an alarm is down
* :link: **history-warp10** : A node for sending variables histories into warp10 timeseries
  * Hold a buffer of variable modifications (with timestamp) and flush it into warp10

## Available config nodes

* :link: **warp10** : A node for configuring warp10 connections.
  * Specify a HTTP endpoint and write token for the connection

## Advanced tips

### Variable naming

Use dot notations for variable names such as `floor1.vent.speed`. Then using read/alarm you can match them by using wildcards, like this : `floor1.vent.*` (the output message will contain a `origin` js object containing the matched variable).

### Single write-variable and multiple variables

You can omit the variable name into the `write-variable` node. Instead, put the variable name into the `topic` alongside the `payload` containing the value.