open-index/open-npm huggingface dataset:
npm package: @meetelise/searchable-react-json-view
Description: Interactive react component for displaying javascript arrays and JSON objects.
Author: Leo Bach
Latest version: 1.0.0

# searchable-react-json-view

This is a fork of [searchable-react-json-view](https://www.npmjs.com/package/searchable-react-json-view).

The only changes made to the original package are:
- The addition of `react@^17` as an accepted peer dependency
- Upgrading the lockfile from v1 to v3

### Install
```sh
yarn add searchable-react-json-view
```

### New Props

Name|Type|Default|Description
|:---|:---|:---|:---
`highlightSearch`|`string`|None|What term to highlight - applies to number, string, boolean and object keys.
`highlightSearchColor`|`string`| <img src="https://user-images.githubusercontent.com/16322616/89119023-9018cb80-d4b3-11ea-8fca-8b068ce8ef71.png"/>|Highlight color
`highlightCurrentSearchColor`|`string`| <img src="https://user-images.githubusercontent.com/16322616/89119031-ac1c6d00-d4b3-11ea-9640-e5320904fdd3.png"/> | Current highlight color
`customCopiedIcon`|`JSX.Element`| null | Custom icon that appears after copying
`customCopyIcon`|`JSX.Element`| null | Custom icon for copy to clipboard
`customActions`|`array`| [] | Custom actions that appear after copy, edit etc. each item should be: { icon: JSX.Element, onClick: clickedJsonValue => void }

### Example

<kbd><img src="https://user-images.githubusercontent.com/16322616/89118875-1d5b2080-d4b2-11ea-81fe-514d019cb26b.png" width="450" /></kbd>

### Custom actions & copy icon
```jsx
<JsonViewer
    customCopiedIcon={<span>Copied</span>}
    customCopyIcon={<span>Copy</span>}
    customActions={[{
        icon: <span>A</span>,
        onClick: (value) => alert(JSON.stringify(value))
    }]}
/>
```
npm package: @meetelise/text-with-us
Description: Text With Us widget, powered by MeetElise
Author: eric@meetelise.com
Latest version: 1.5.5

# \<meetelise-sms-number-input>

Text-with-us widget, powered by MeetElise.

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

## Installation

```bash
npm i meetelise-sms-number-input
```

## Usage

```html
<script type="module">
  import 'meetelise-sms-number-input/meetelise-sms-number-input.js';
</script>

<meetelise-sms-number-input></meetelise-sms-number-input>
```

## Linting and formatting

To scan the project for linting and formatting errors, run

```bash
npm run lint
```

To automatically fix linting and formatting errors, run

```bash
npm run format
```

## Testing with Web Test Runner

To execute a single test run:

```bash
npm run test
```

To run the tests in interactive watch mode run:

```bash
npm run test:watch
```

## Demoing with Storybook

To run a local instance of Storybook for your component, run

```bash
npm run storybook
```

To build a production version of Storybook, run

```bash
npm run storybook:build
```


## Tooling configs

For most of the tools, the configuration is in the `package.json` to reduce the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `web-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @meetfranz/electron-cookies
Description: Provides document.cookie support for Electron
Latest version: 3.0.2

# electron-cookies

Provides document.cookie support for Electron. For use with Amplitude and Google Analytics in Electron.

The underlying cookie implementation is Salesforce's [`tough-cookie`](https://github.com/SalesforceEng/tough-cookie) library and Exponent's [WebStorageCookieStore](https://github.com/exponentjs/tough-cookie-web-storage-store) for persistence.

## Installation

```sh
npm install @meetfranz/electron-cookies --save
```

## Usage

```js
import ElectronCookies from "@meetfranz/electron-cookies";

// Add support for document.cookie, using the given origin (protocol, host, and
// port)
ElectronCookies.enable({
  origin: "https://example.com",
});

// Remove support for document.cookie. Cookies are not cleared from the
// underlying storage.
ElectronCookies.disable();
```

## Behavior

When getting or setting a cookie, the browser needs to know the current URL of the page.

In Electron, HTML files are usually served from the local filesystem, which has no domain. electron-cookies provides you a way to specify the origin of the URL to use:

```js
ElectronCookies.enable({ origin: "https://example.com" });
```

This tells electron-cookies the origin of the URL to use when accessing cookies. The path of the URL is the relative path from the app's root to the path of the HTML file. So if the app is at `/Users/you/Desktop/` and the HTML file is at `/Users/you/Desktop/web/index.html`, the synthesized URL will be `https://example.com/web/index.html`.

Alternatively, if you omit an origin, the full `file:` URL of the HTML file is used instead.

## Google Analytics

To use Google Analytics in Electron, we use code like this:

```html
<script>
  (function (i, s, o, g, r, a, m) {
    i["GoogleAnalyticsObject"] = r;
    (i[r] =
      i[r] ||
      function () {
        (i[r].q = i[r].q || []).push(arguments);
      }),
      (i[r].l = 1 * new Date());
    (a = s.createElement(o)), (m = s.getElementsByTagName(o)[0]);
    a.async = 1;
    a.src = g;
    m.parentNode.insertBefore(a, m);
  })(
    window,
    document,
    "script",
    "https://www.google-analytics.com/analytics.js",
    "ga"
  );

  (() => {
    "use strict";
    let ElectronCookies = require("@meetfranz/electron-cookies");
    ElectronCookies.enable({ origin: "https://example.com" });

    ga("create", GOOGLE_ANALYTICS_ID, "auto");
    ga("set", "location", "https://example.com/");
    ga("set", "checkProtocolTask", null);
    ga("send", "pageview");
  })();
</script>
```

Notable changes to the standard code include:

- The analytics script URL is prefixed with `https:` instead of inheriting the page's protocol
- We enable `electron-cookies`
- We set the `location` field in Google Analytics
- The `checkProtocolTask` field is set to null to disable checking for a `file:` protocol
npm package: @meetfranz/electron-notification-state
Description: Should you send a notification?
Author: Felix Rieseberg
Latest version: 1.0.0

# electron-notification-state
Should you display a notification to your user? This module allows you to check.

## Usage

### Do Not Disturb / Quiet Hours
```js
const { getDoNotDisturb } from 'electron-notification-state'
// On Windows, logs `true` if "quiet hours" are enabled
// On macOS, logs `true` if "do not disturb" is enabled
console.log(getDoNotDisturb());
```

### Session State
On Windows, you likely want to check [SHQueryUserNotificationState](https://msdn.microsoft.com/en-us/library/windows/desktop/bb762242(v=vs.85).aspx), checking whether or not a screensaver is running, if the screen is locked, or if a presentation is running. On macOS, you likely want to check if the screen is locked and if the if the user has an active screen session.

The call below logs a different string, depending on the platform:
#### macOS
- `SESSION_SCREEN_IS_LOCKED` The screen is locked.
- `SESSION_ON_CONSOLE_KEY` The user currently has console/graphical control.

#### Windows
- `QUNS_NOT_PRESENT` A screen saver is displayed, the machine is locked, or a nonactive Fast User Switching session is in progress.
- `QUNS_BUSY` A full-screen application is running or Presentation Settings are applied. Presentation Settings allow a user to put their machine into a state fit for an uninterrupted presentation, such as a set of PowerPoint slides, with a single click.
- `QUNS_RUNNING_D3D_FULL_SCREEN` A full-screen (exclusive mode) Direct3D application is running.
- `QUNS_PRESENTATION_MODE` The user has activated Windows presentation settings to block notifications and pop-up messages.
- `QUNS_ACCEPTS_NOTIFICATIONS` None of the other states are found, notifications can be freely sent.
- `QUNS_QUIET_TIME` Introduced in Windows 7. The current user is in "quiet time", which is the first hour after a new user logs into his or her account for the first time. During this time, most notifications should not be sent or shown. This lets a user become accustomed to a new computer system without those distractions. Quiet time also occurs for each user after an operating system upgrade or clean installation, according to Windows. This is _not_ the same as "quiet hours".
Note that during quiet time, if the user is in one of the other blocked modes (QUNS_NOT_PRESENT, QUNS_BUSY, QUNS_PRESENTATION_MODE, or QUNS_RUNNING_D3D_FULL_SCREEN) SHQueryUserNotificationState returns only that value, and does not report QUNS_QUIET_TIME.
- `QUNS_APP` Introduced in Windows 8. A Windows Store app is running.

```js
const { getSessionState } from 'electron-notification-state'

console.log(getSessionState());
```

## License
MIT. Please see LICENSE for details.
npm package: @meetfranz/macos-notification-state
Description: macOS notification state as a native node addon
Author: Felix Rieseberg
Latest version: 1.3.7

## macos-notification-state
Do you want to check if you should display a notification to your user on macOS? This native module checks if the user is active, if the screen is locked, or if "do not disturb" is enabled.

```
npm install macos-notification-state
```

```
const { getNotificationState, getSessionState, getDoNotDisturb } = require('macos-notification-state`)

// This will brint a boolean (true if enabled, false if not)
console.log(getDoNotDisturb())

// This will print a string indiciating the current state, being one of the following:
// 'SESSION_SCREEN_IS_LOCKED'
// 'SESSION_ON_CONSOLE_KEY'
// 'DO_NOT_DISTURB'
// 'UNKNOWN'
// 'UNKNOWN_ERROR'
//
// If "do not disturb" is enabled, it takes precedence.
console.log(getNotificationState())

// This will print a string indiciating the current session state, being one of the following:
// 'SESSION_SCREEN_IS_LOCKED'
// 'SESSION_ON_CONSOLE_KEY'
// 'UNKNOWN'
console.log(getSessionState())
```

#### License
MIT, please see LICENSE for details. Copyright (c) 2019 Felix Rieseberg.
npm package: @meetgradient/mspc-sdk
Description: Lightweight JavaScript/TypeScript SDK for integrating with the MSPCentric platform
Author: MSPCentric
Latest version: 0.3.0-alpha.6

# MSPC SDK

Lightweight JavaScript/TypeScript SDK for integrating with the MSPC platform.

## Installation

```bash
npm install @meetgradient/mspc-sdk
```

## Features

- Real-time updates via Server-Sent Events (SSE)
- Simplified reconcile and alerting API

## Quick Start

```typescript
import { MspcSdk } from '@meetgradient/mspc-sdk';

// Initialize the SDK
const sdk = new MspcSdk({
  apiKey: 'your-api-key',
  apiSecret: 'your-api-secret',
  baseUrl: 'https://cybersoft.mspcentric.app.com',
  stream: true,
  fallbackToPolling: true,
});

// Subscribe to events
sdk.on('mspc.sdk.connected', () => {
  console.log('Connected to MSPC');
});

sdk.on('mspc.alerts.status_update', (event) => {
  console.log('Alert status update:', event);
});

// Connect to MSPC
await sdk.connect();

// Submit an alert
const correlationId = await sdk.alerts.createAlert({
  organizationOemToken: 'token',
  integrationId: 'integration-id',
  title: 'Critical Alert',
  summary: 'System detected critical issue',
  alertType: 'malware-blocked',
  accountId: 'account-123',
  productGroup: 'Security',
  incidentStatus: 'open',
});

console.log('Alert submitted:', correlationId);
```

## Documentation

Full documentation will be available at [docs link].

## Requirements

- Node.js 18 or higher
- TypeScript 5.0+ (for TypeScript projects)

## License

MIT