open-index/open-npm huggingface dataset:
npm package: @heavyai/heavydb-thrift-ts-bindings
Description: HeavyDB Thrift TypeScript bindings
Latest version: 0.0.8

# heavydb-thrift-ts-bindings

HeavyDB Thrift TypeScript bindings

## How to update bindings

* Install+start docker
* `npm ci`
* `npm run updateLib`

## How to publish package to NPM

* Cut a release branch off latest `master`: `git checkout -b releases/[semver]`
* `npm version [major|minor|patch]`
* `git push origin <release branch name> && git push origin --tags`
* `npm publish` (This command will fail if you don't have write access to https://www.npmjs.com/package/@omnisci/omniscidb-thrift-ts-bindings)
* Open a PR to merge the release branch
* Create a new GitHub Release off of the new tag the `npm version` command above produced.
npm package: @heavybit/hb-shared-utils-package
Description: Shared utils package that allows microservices to use common methods and data
Author: Nicholas Kute
Latest version: 1.0.50

# Shared Cache Package with Bull

This is a shared caching library for microservices using Bull and Redis. It processes cache requests (get, set, delete) asynchronously using queues, providing scalability and resilience.

## Installation

1. Install the package:

   ```
   npm install shared-cache-package
   ```
npm package: @heavycircle/remark-obsidian
Description: A remark plugin to support Obsidian-flavored Markdown (renamed from @thecae/remark-obsidian)
Author: heavycircle
Latest version: 1.1.11

# remark-obsidian

A [remark](https://github.com/remarkjs/remark) plugin to extend support to [Obsidian](https://obsidian.md/)-flavored Markdown.

## Contents

- [What is this?](#what-is-this)
- [Install](#install)
- [Use](#use)
- [API](#api)
- [Security](#security)
- [License](#license)

## What is this?

This package is a [unified](unified) ([remark](https://github.com/remarkjs/remark)) package that extends Markdown to support [Obsidian flavors](https://help.obsidian.md/Editing+and+formatting/Obsidian+Flavored+Markdown).

The list of Supported Obsidian Markdown items are:

| **Syntax**      | **Description**  |
| --------------- | ---------------- |
| `[[Link]]`      | Internal Links   |
| `![[Link]]`     | Embed Files      |
| `![[Link#^id]]` | Block References |
| `^id`           | Defining a Block |
| `%%Text%%`      | Comments         |
| `~~Text~~`      | Strikethroughs   |
| `==Text==`      | Highlights       |
| ` ``` `         | Code Blocks      |
| `- [ ]`         | Incomplete Task  |
| `- [x]`         | Completed Task   |
| `[!note]`       | Callouts         |

_Obsidian's website notes that not all these are fully Obsidian-specific. The main reason I wrote this plugin is for Link and Callout support_.

## Install

This package is [ESM only](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c). In Node.js (version 16+), install using [`npm`](https://docs.npmjs.com/cli/install):

```bash
npm install @heavycircle/remark-obsidian
```

## Use

Most definitions are self-explanatory from the above table. However, it is worth mentioning the various Callout syntaxes available.

Use the [Obsidian Callouts](https://help.obsidian.md/Editing+and+formatting/Callouts) guide for further instruction.

This plugin is best used with [remark-gfm](https://www.npmjs.com/package/remark-gfm), [rehype-raw](https://www.npmjs.com/package/rehype-raw), and [remark-wiki-link-plus](https://www.npmjs.com/package/remark-wiki-link-plus).

## API

This package exports no identifiers. The default export is `remarkObsidian`.

#### `unified().use(remarkObsidian)`

Provides support for Obsidian-flavored Markdown, including tables, callouts, links, embeds, and more.

To get full use of the package, ensure you include Obsidian-compliant variables. Then, import the CSS file inside the `global.css` file:

```css
@import "@heavycircle/remark-obsidian/obsidian.module.css";
```

###### Parameters

There are no parameters.

###### Returns

Transform ([`Transformer`](https://github.com/unifiedjs/unified#transformer)).

# Security

Use of remark-videos does not involve [rehype](https://github.com/rehypejs/rehype) ([hast](https://github.com/syntax-tree/hast)) or user content so there are no openings for [cross-site scripting (XSS)](https://en.wikipedia.org/wiki/Cross-site_scripting) attacks.


# License

[MIT](LICENSE) &copy; heavycircle
npm package: @heavyind/array-utils
Description: Array utilities used by Heavy Industries
Author: Heavy Industries
Latest version: 0.0.3

# Heavy Industries array utilities

A small library of things Heavy Industries uses all the time.

A complete API documentation can be found [in the Wiki](https://github.com/chaseries/hi-array-utils/wiki/API-documentation).

## Installation

Via npm:

```
npm install --save @heavyind/array-utils
```

Via yarn:

```
yarn add @heavyind/array-utils
```

Via unpkg (exposed as `HiArrayUtils`):

```
<script src="https://unpkg.com/@heavyind/array-utils"></script>
```

## License

MIT
npm package: @heavyind/vue-modal
Description: A modal plugin for Vue projects
Author: Heavy Industries
Latest version: 0.0.5

# Heavy Industries vue-modal

**Note** This is highly experimental. It could spontaneously combust while using.

## What it is

A plugin to add modal functionality to a Vue application. It depends on Vuex.

## What it *isn't*

It is not a kitchen sink solution, nor is it even a modal component. There are plenty of fantastic packages out there already for those looking for pre-built components.

This project is rather a Vuex API for *handling* modal components. It is abstracted out for the sake of consistency and simplicity across projects, and eschews complex configurations objects and stylistic assumptions. It requires a little more boilerplate, but its minimal interface demands little familiarity with anything other than Vue itself.

## Installation

Via npm:

```
npm i --save @heavyind/vue-modal
```

Via yarn:

```
yarn add @heavyind/vue-modal
```

Via unpkg:

```
<script src="https://unpkg.com/@heavyind/vue-modal"></script>
```

## Usage

### Getting started

Pass a configuration object containing your store into the plugin:

```
import VueModalPlugin from "@heavyind/vue-modal";

Vue.use(VueModalPlugin, { store })
```

By default, you must access the API by assigning it to component properties and methods (mapState, mapActions).


## Configuration

Configuration must include the Vuex store object that you intend to use.

### Default

The default configuration object has the following form:

```
{ store: null,
  mixin: false, 
  mixinNamespace: "$modal"
  storeNamespace: "modal"
}
```

### Configuration in-depth

`store`

The Vuex store you intend to use.

`mixin`

A boolean representing whether or not the plugin should attach a global mixin that allows you to access properties and methods on each object. This mixin will be scoped to `mixinNamespace`, which defaults to `"$modal"`.

`storeNamespace`

The namespace of the VueModal module in your Vuex store. Defaults to `"modal"`.

`mixinNamespace`

The name bound to each component that allows you to easily access modal properties and methods, should `mixin` be set to `true`. Defaults to `"$modal"` (e.g., `this.modal.open`);

## API

`isOpen`

The open state of the modal.

`settings`

The settings object, which takes the form `{ component, props }`, where `component` represents the optional component inside the modal and `props` represents the optional props of that component.

`component`

An alias of `settings.component`.

`props`

An alias of `settings.props`.

`open`

Sets `open` state to `true`.

`openWith` 

Sets `open` state to true and stores a settings object of type `{ component: Component, props: Object }` which contains the current modal component and any props that should be passed to it.

`close`

Sets the `open` state to false.

`toggle`

Sets the `open` state to `!open`.

`setComponent`

Sets the inner component of the modal.

`setProps`

Sets any props you would like to pass to the inner component of the modal.

## License

MIT
npm package: @heavyind/vue-transit
Description: Transition animations for route changes
Author: Heavy Industries
Latest version: 0.0.4

# Vue Transit

An alternative to Vue's native transition component that is designed to be used for more sophisticated page enter and leave animations than what's currently feasible out-of-the-box.

## What

Vue Transit does not remove elements from the DOM, but instead applies arbitrary styles based on page enter and page leave. In practice, this can mean something like setting the opacity of the element to `1` from `0` on page enter, or doing the opposite on page leave.

### Why not just use the native `<transition>` component?

To begin with, it's actually not terribly flexible for animation. The API is, in the author's mind, good but insufficient to achieve complex, fancy transitions, and a wrapper must be put around it. Moreover, there is no way to stop Vue's native `<transition>` from removing the element from the DOM. If elements' positionings depend on one another (e.g., `relative`) on an outgoing page, removing those elements at different times will cause serious problems.

## Basic usage

1. Initialize the component somewhere in the root component of the app's `mounted` function.
2. Use `<transit-view>` instead of `<router-view>`.
3. Replace native `<router-link>` elements with `<transit-link>`.
4. Wrap the element in question with a `<transit>` tag.

## API

The elements can be configured with a duration, delay, timing functions, and other options.