open-index/open-npm huggingface dataset:
npm package: @narative/oanda-v20
Description: OANDA v20 bindings for Javascript
Author: OANDA Corporation
Latest version: 3.0.54

# OANDA v20 (Narative fork)

## Why

- Typescript friendly (WIP)
- Bug fixing

## Installation

```shell
yarn add @narative/oanda-v20
```

## Usage

```javascript
import * as oandaAPI from '@narative/oanda-v20'

const client = new oandaAPI.Rest('my-app-name', '1234567890qwfpgjluy1234567890', true) // user token on OANDA practice server
const result = await client.account.list()
console.log('OANDA result', result) // should show the data from GET /v3/accounts (https://developer.oanda.com/rest-live-v20/account-ep/)
```

## Publish

- update version in package.json
- `yarn build`
- `npm publish`
npm package: @narayanan1994/test-ng-lib
Description: angular library publish testing
Author: Narayanan
Latest version: 0.0.1-beta

# TestNgLib

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.

## Code scaffolding

Run `ng generate component component-name --project test-ng-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project test-ng-lib`.
> Note: Don't forget to add `--project test-ng-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build test-ng-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build test-ng-lib`, go to the dist folder `cd dist/test-ng-lib` and run `npm publish`.

## Running unit tests

Run `ng test test-ng-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @narayanan1994/test-registry-npmjs
Description: angular library publish testing
Author: Narayanan
Latest version: 0.0.2

# test-registry-npmjs
To test library public angular library publishing to https://registry.npmjs.com/

# version
0.0.2

# test-registry-npmjs
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 17.3.0.

## Code scaffolding

Run `ng generate component component-name --project test-ng-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project test-ng-lib`.
> Note: Don't forget to add `--project test-ng-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build test-ng-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build test-ng-lib`, go to the dist folder `cd dist/test-ng-lib` and run `npm publish`.

## Running unit tests

Run `ng test test-ng-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI Overview and Command Reference](https://angular.io/cli) page.
npm package: @narciso/tiptap-extension-global-drag-handle
Description: drag handle extension for tiptap
Author: Narciso Guillen
Latest version: 0.1.18

# Tiptap Extension: GlobalDragHandle
<a href="https://www.npmjs.com/package/tiptap-extension-global-drag-handle"><img alt="NPM Downloads" src="https://img.shields.io/npm/dw/tiptap-extension-global-drag-handle"></a>


## Install

NPM
```
$ npm install @narciso/tiptap-extension-global-drag-handle
```

Yarn
```
$ yarn add @narciso/tiptap-extension-global-drag-handle
```

## Usage

```js
import GlobalDragHandle from 'tiptap-extension-global-drag-handle'

new Editor({
  extensions: [
    GlobalDragHandle,
  ],
})
```

In order to enjoy all the advantages of the drag handle, it is recommended to install the [AutoJoiner](https://github.com/NiclasDev63/tiptap-extension-auto-joiner) extension as well, which allows you to automatically join various nodes such as 2 lists that are next to each other.

## Configuration

Optionally, you can also configure the drag handle.

```js
import GlobalDragHandle from 'tiptap-extension-global-drag-handle'

new Editor({
  extensions: [
    GlobalDragHandle.configure({
        dragHandleWidth: 20, // default

        // The scrollTreshold specifies how close the user must drag an element to the edge of the lower/upper screen for automatic 
        // scrolling to take place. For example, scrollTreshold = 100 means that scrolling starts automatically when the user drags an 
        // element to a position that is max. 99px away from the edge of the screen
        // You can set this to 0 to prevent auto scrolling caused by this extension
        scrollTreshold: 100, // default

        // The css selector to query for the drag handle. (eg: '.custom-handle').
        // If handle element is found, that element will be used as drag handle. 
        // If not, a default handle will be created
        dragHandleSelector: ".custom-drag-handle", // default is undefined


        // Tags to be excluded for drag handle
        // If you want to hide the global drag handle for specific HTML tags, you can use this option.
        // For example, setting this option to ['p', 'hr'] will hide the global drag handle for <p> and <hr> tags.
        excludedTags: [], // default

        // Custom nodes to be included for drag handle
        // For example having a custom Alert component. Add data-type="alert" to the node component wrapper.
        // Then add it to this list as ['alert']
        //
        customNodes: [],
    }),
  ],
})
```

## Styling
By default the drag handle is headless, which means it doesn't contain any css. If you want to apply styling to the drag handle, use the class "drag-handle" in your css file.
Take a look at [this](https://github.com/steven-tey/novel/blob/main/apps/web/styles/prosemirror.css#L131) example, to see how you can apply styling.
npm package: @nardgl/gltf-parser
Description: partially parses GLTF(JSON flavor)
Author: Mathieu Mence
Latest version: 1.0.5

# `@nardgl/gltf-parser`

Partially parses GLTF(json flavor)

## Usage

```
const gltfParser = require('@nardgl/gltf-parser');

// TODO: DEMONSTRATE API
```
npm package: @nardole/vite-plugin-mockoon
Description: Run Mockoon with your Vite dev server using a tiny plugin.
Author: Nardole Labs
Latest version: 1.0.2

# @nardole/vite-plugin-mockoon

Run Mockoon alongside your Vite dev server using a tiny plugin. It spawns the Mockoon CLI when Vite starts and stops it when Vite shuts down.

- Zero-config start with a Mockoon data file
- Works on macOS, Linux, and Windows
- Pass any extra Mockoon CLI flags you need

## Installation

npm:

- npm install -D @nardole/vite-plugin-mockoon @mockoon/cli

Yarn:

- yarn add -D @nardole/vite-plugin-mockoon @mockoon/cli

pnpm:

- pnpm add -D @nardole/vite-plugin-mockoon @mockoon/cli

Note: The plugin launches the `mockoon-cli` binary. Installing `@mockoon/cli` locally ensures the command is available on your PATH when running Vite scripts.

## Usage

vite.config.ts:

- import { defineConfig } from 'vite'
- import { mockoonPlugin } from '@nardole/vite-plugin-mockoon'
-
- export default defineConfig({
-   plugins: [
-     mockoonPlugin({
-       dataPath: './mockoon/data.json',
-       // Optional: forward any CLI flags
-       args: ['--port', '3001']
-     })
-   ]
- })

When you run `vite` or `vite dev`, the plugin will start Mockoon with the provided data file and extra flags.

## Options

- dataPath (string | string[]): Required. Path to a Mockoon data file (.json) or an array of files.
- stdio (StdioOptions): Optional. How to connect the child process stdio. Defaults to "ignore". Use "inherit" to see Mockoon logs in your terminal.
- args (string[]): Optional. Additional CLI arguments to pass to Mockoon, e.g. ["--port", "3001", "--hostname", "0.0.0.0"].
- command (string): Optional. Binary to execute. Defaults to "mockoon-cli".
- autoStart (boolean): Optional. Start automatically with the Vite dev server. Defaults to true.
- stopOnExit (boolean): Optional. Try to stop the Mockoon process when Vite exits. Defaults to true.

Notes:

- If you provide multiple data files, the plugin passes multiple `--data <file>` flags to the Mockoon CLI.
- For available flags, refer to Mockoon CLI docs: https://github.com/mockoon/mockoon/tree/main/packages/cli

## Recipes

- Show Mockoon logs in the same terminal:

- mockoonPlugin({ dataPath: './mock.json', stdio: 'inherit' })

- Run on a specific port and hostname:

- mockoonPlugin({ dataPath: './mock.json', args: ['--port', '3100', '--hostname', '127.0.0.1'] })

- Multiple environments (multiple data files):

- mockoonPlugin({ dataPath: ['./mock-1.json', './mock-2.json'] })

## Development

- pnpm i
- pnpm build

This repository uses `tsup` to build ESM output and TypeScript declarations. The plugin source is in `src/` and the built files are emitted to `dist/`.

### Release

1. Bump the version in package.json
2. Build: `npm run build`
3. Publish: `npm publish --access public`

## Contributing

Contributions are welcome! Please read CONTRIBUTING.md for local setup and guidelines.

## License

MIT © Nardole Labs