open-index/open-npm huggingface dataset:
npm package: @qlik/carbon-core
Description: Core components for react-native-carbon
Author: Qlik
Latest version: 2.1.0

# carbon (WIP)

## A React Native Nebula Engine

> _The atoms of carbon can bond together in diverse ways, resulting in various allotropes of carbon. Well-known allotropes include graphite, diamond, amorphous carbon, fullerenes, and React Native Supernovae._

This project renders nebula supernovae in the React Native context.  It renders Picasso Charts natively on the device without a need of the webview.

## Installing

### This is a WIP

`yarn add ssh://git@github.com:qlik-trial/carbon.git#workspace=sn-treemap`

### Limitations

- Since data has to be passed over to the native bridge, and React Native does not fully support JSI, at time of this writing, input(interactions) data is throttled to every 30ms
- When remote debugging, performance will be extremly slow, since it is literally running the javascript on the desktop and data has to be transfered from the desktop to the device.
- Android does not have the best JavaScript engine for React Native.  As a result, the custom carbon renderer, uses its own scene and uses a Quadtree for the broad-phase collision detection.  There is still some work left to be done.  The only narrow-phase support at this momoment is Axis-Aligned-Rects.  However, it imports the code from picasso.js to accomplish the narrow-phase.

## Kinesics

> _The study of the way in which certain body movements and gestures serve as a form of nonverbal communication._

This project uses a custom interaction manager named kinesics.  It is backward compatible with the hammer plugin.   Currently only "Pan" is supported.

### Example usage

```javascript
 const interactionType = env.carbon ? 'kinesics' : 'hammer';
 const interactions = [
    {
      type: interactionType,
      gestures: [
        {
          type: 'Pan',
          events: {
            panstart: function onPanStart(e) {
              this.chart.component('lassoComp').emit('lassoStart', e);
            },
            pan: function onPan(e) {
              this.chart.component('lassoComp').emit('lassoMove', e);
            },
            panend: function onPanEnd(e) {
              this.chart.component('lassoComp').emit('lassoEnd', e);
            },
          },
        },
      ],
    },
  ];

```
npm package: @qlik/carboncopy
Description: A react-native template project to create supernovas in react-native
Author: Vittorio Cellucci
Latest version: 1.1.5

# CarbonCopy
A react-native template project to create supernovas in react-native

## Prerequisite
* React native dev environment installed
* A QCS account with an API Key
* VSCode highly recommended with react native extension installed

## Usage
1. `npx @qlik/carboncopy <MyAppName> <viztype> <pathToDevSN>`
2.  Open <MyAppName>/package.json and change the name to your app
3.  Open the the folder in VSCode
npm package: @qlik/design-tokens
Description: Design tokens for Qlik UI's
Latest version: 1.1.2

# Design Tokens

This is a repository stores the single source of truth for tokens `/tokens` and the generated output in all the following formats: css, js, json.

---

## How to run and try it out

`pnpm gen-tokens` will compile together a token set from the default values for all token-modules.

You can open the `token-test.html` locally to see the result of the default token configuration and modify the imports to run against custom modules.

## How it works

The token source is owned and updated by the System Design team through a Figma extension called [Token Studio](https://tokens.studio/). We are using the package `@qlik/sprout-cli` to generate the output.
npm package: @qlik/react-native-carbon
Description: React Native nebula engine
Author: Qlik
Latest version: 2.1.33

# react-native-carbon

<img src="logo/Carbon.png" height="256"/>

React Native nebula engine

## Running the example
This uses symlinks.  In order to develop and run the sample @qlik/react-native-helium and @qlik/carbon-core have to be cloned in the same root directory as @qlik/react-native-carbon

Recommend way is to create a folder called "Carbon" and clone dependencies in there.
They should all be in the same root folder.
1. clone react-native-helium
2. clone me
3. clone carbon-core
4. cd into react-native-carbon
5. yarn dev-setup
6. in example/Galaxy create a galaxy.json with the following

```
{
  "tenantDomain": <your tenant>,
  "apiKey":<your api key>,
  "appId": <app id>,
  "modelId": <id of visualization>
}
```

## Interactions run on the UI Thread
To improve performance all interactions are run on the UI thread using react-native-helium.

## License

MIT
npm package: @qlik/sprout-css-modules
Description: Collections of CSS modules ready to be used to implement sprout
Latest version: 6.43.6

# @qlik/sprout-css-modules

This package contains CSS modules implementation of a [tailwindcss](https://tailwindcss.com/) like api. We are picking names from it to give access to sprout design-tokens in a way it is easier for everyone regardless the use of any frontend framework.

We are limiting the number of selectors to only being core class of tailwindcss. We do not want to support prefixed class like `dark:` or `md:`.

## How to use

```tsx
import sprout from "@qlik/sprout-css-modules";

// you can use sprout.classNames with React like this
function MyComponent(props) {
  return (
    <div
      className={sprout.classNames("p-m", "flex", {
        "flex-col": !!props.condition,
      })}
    >
      hello world
    </div>
  );
}
```

If you are using `@qlik/sprout-react` you can directly import classNames from it which is convinient because it uses a named export

```ts
import { classNames } from "@qlik/sprout-react";
```

## How to contribute

We will accept any classNames that exists in tailwindcss `core` as mentionned (no prefix) and that is usefull to build application on top of sprout.
npm package: @qlik/sprout-gesture
Description: This package contains the react implementation of [Components 2.0](https://www.figma.com/file/HmokLgpDo4ogI5l5hpNApf/Sprout-Core-Components) using [React](https://react.dev/) and our `@qlik-trial/sprout-css-modules`
Latest version: 0.0.3

# @qlik-trial/sprout-css-react

This package contains the react implementation of [Components 2.0](https://www.figma.com/file/HmokLgpDo4ogI5l5hpNApf/Sprout-Core-Components) using [React](https://react.dev/) and our `@qlik-trial/sprout-css-modules`

## How to use

You can install it as any npm dependencies in your project and start to use it.

## Create a new Component

We will list here a few guidelines about quality and API

A component must provide:

- documentation (link to figma, api, ...)
- visual tests: One VisualTest story with all possible visual combination
- [accessibility tests](https://playwright.dev/docs/accessibility-testing)

A component must avoid:

- external library that render HTML
- [context](https://react.dev/learn/passing-data-deeply-with-context) as this make the library harder to udpate.
- translations (which needs external library)
npm package: @qlik/sprout-react
Description: This package contains the react implementation of [Components 2.0](https://www.figma.com/file/HmokLgpDo4ogI5l5hpNApf/Sprout-Core-Components) using [React](https://react.dev/) and our `@qlik/sprout-css-modules`
Latest version: 6.45.2

# @qlik/sprout-react

This package contains the react implementation of [Components 2.0](https://www.figma.com/file/HmokLgpDo4ogI5l5hpNApf/Sprout-Core-Components) using [React](https://react.dev/) and our `@qlik/sprout-css-modules`

## How to use

You can install it as any npm dependencies in your project and start to use it.

## Create a new Component

We will list here a few guidelines about quality and API

A component must provide:

- documentation (link to figma, api, ...)
- visual tests: One VisualTest story with all possible visual combination
- [accessibility tests](https://playwright.dev/docs/accessibility-testing)

A component must avoid:

- external library that render HTML
- [context](https://react.dev/learn/passing-data-deeply-with-context) as this make the library harder to udpate.
- translations (which needs external library)
npm package: @qlik/sprout-react-table
Description: This package provide an easy to use `Table` component from Sprout Design System based on
Latest version: 0.16.6

# @qlik/sprout-react-table

This package provide an easy to use `Table` component from Sprout Design System based on

- `@qlik/sprout-react`
- `@tanstack/react-table`
- `@tanstack/react-virtual`
npm package: @qlin/eslint-linter-browserify
Description: Use eslint in the browser
Author: Tony Brix
Latest version: 8.56.0

# eslint-linter-browserify
Use eslint in the browser

```js
import * as eslint from "eslint-linter-browserify";

// or const eslint = require("eslint-linter-browserify");
// or <script src="https://cdn.jsdelivr.net/npm/eslint-linter-browserify/linter.js"></script>
// or <script src="https://cdn.jsdelivr.net/npm/eslint-linter-browserify/linter.min.js"></script>

const linter = new eslint.Linter();

const messages = linter.verify("var foo;", {
  rules: {
    semi: ["error", "never"]
  }
}, { filename: "foo.js" });

console.log(messages);
```

https://eslint.org/docs/developer-guide/nodejs-api#linter

See the [CodeMirror example](./example) for a way to use this in [CodeMirror](https://codemirror.net).
npm package: @qlin/process
Description: process information for node.js and browsers
Author: Roman Shtylman
Latest version: 0.11.11

# process

fork [node-process](https://github.com/defunctzombie/node-process)

will merge process.env, to compatible vite define in dev;

## user

```require('process');``` just like any other module.

Works in node.js and browsers via the browser.js shim provided with the module.

## browser implementation

The goal of this module is not to be a full-fledged alternative to the builtin process module. This module mostly exists to provide the nextTick functionality and little more. We keep this module lean because it will often be included by default by tools like browserify when it detects a module has used the `process` global.

It also exposes a "browser" member (i.e. `process.browser`) which is `true` in this implementation but `undefined` in node. This can be used in isomorphic code that adjusts it's behavior depending on which environment it's running in. 

If you are looking to provide other process methods, I suggest you monkey patch them onto the process global in your app. A list of user created patches is below.

* [hrtime](https://github.com/kumavis/browser-process-hrtime)
* [stdout](https://github.com/kumavis/browser-stdout)

## package manager notes

If you are writing a bundler to package modules for client side use, make sure you use the ```browser``` field hint in package.json.

See https://gist.github.com/4339901 for details.

The [browserify](https://github.com/substack/node-browserify) module will properly handle this field when bundling your files.
npm package: @qlonolink/n8n-nodes-qaip
Description: n8n community nodes for integrating with QAIP API.
Author: Qlonolink
Latest version: 1.0.2

# n8n-nodes-qaip

This is an n8n community node. It lets you use [QAIP](https://developer.qaip.com/) in your n8n workflows.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/sustainable-use-license/) workflow automation platform.

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

The node supports the following operations:

- **Completion**: Generate AI responses in a natural conversational format based on your data sources.
- **Extract**: Extract information from unstructured data and convert it into structured JSON data according to a specified JSON schema.
- **Search**: Retrieve relevant information from your data sources using semantic search based on your queries.

See the [QAIP API documentation](https://developer.qaip.com/docs/sdks) for more details on each operation.

## Examples

You can find example workflows in the [examples/](./examples/) folder. To use them:

1. Copy the JSON content of the workflow file.
2. In n8n, press `Cmd + V` (Mac) or `Ctrl + V` (Windows) to paste the workflow.
3. Configure the required credentials for the nodes. Refer to the [QAIP documentation](https://developer.qaip.com/docs/features/apikey) to create an API key.

Refer to the [n8n documentation](https://docs.n8n.io/workflows/export-import/) for more details on how to import workflows.

### Simple Completion

- **File**: [`qaip_simple_completions.json`](./examples/qaip_simple_completions.json)
- **Description**: A basic workflow demonstrating how to generate a simple completion using the QAIP node.
- **Setup**: Requires [QAIP API key](https://developer.qaip.com/docs/features/apikey). Change the message content to your own prompt.

### Slack Chatbot

- **File**: [`qaip_slack_completions.json`](./examples/qaip_slack_completions.json)
- **Description**: A chatbot that replies to Slack mentions using QAIP. It listens for `app_mention` events and sends a response back to the same thread.
- **Setup**: Requires both QAIP and Slack credentials. Ensure your Slack App is configured to receive `app_mention` events and has the `chat:write` scope. See the [n8n Slack Trigger node documentation](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.slacktrigger/) on how to set up a Slack trigger node.

## Credentials

Refer to [QAIP documentation](https://developer.qaip.com/docs/features/apikey) to create an API key.

## Resources

- [n8n community nodes documentation](https://docs.n8n.io/integrations/#community-nodes)
- [QAIP documentation](https://developer.qaip.com/docs/)