open-index/open-npm huggingface dataset:
npm package: @jspc/react-leaflet-curve
Description: Bezier Curves as React compoment for Leaflet
Author: EPOZ, jspc
Latest version: 3.0.0

# react-leaflet-curve
Bezier Curve - a React component build on top of [React-Leaflet](https://github.com/PaulLeCam/react-leaflet) that integrate [leaflet-curve](https://github.com/elfalem/Leaflet.curve) feature.

![Curve example](images/example.png)


# Getting started

```
import React from 'react';
import { Map, Circle, TileLayer, LayersControl, FeatureGroup, Marker, Polyline } from 'react-leaflet'
import { Curve } from 'react-leaflet-curve'

const path = ['M', [50.14874640066278, 14.106445312500002],
  'Q', [51.67255514839676, 16.303710937500004],
  [50.14874640066278, 18.676757812500004],
  'T', [49.866316729538674, 25.0927734375]]

<Curve positions={path} option={{color:'red',fill:true}}/>
```

For more details on how to use this plugin check the example.

### API

|Command|Parameters|Description|
|-------|----------|-----------|
|M|[lat,lng]+|move to [lat,lng]|
|L|[lat,lng]+|line to [lat,lng]|
|H|[lng]+|horizontal line to [lng]|
|V|[lat]+|vertical line to [lat]|
|C|([lat1,lng1],[lat2,lng2],[lat,lng])+|cubic Bézier curve to [lat,lng] with control points at [lat1,lng1] and [lat2,lng2]|
|S|([lat2,lng2],[lat,lng])+|cubic bézier curve to [lat,lng] with control points at reflection of second control point of previous curve [lat1,lng1] and [lat2,lng2]|
|Q|([lat1,lng1],[lat,lng])+|quadratic Bézier curve to [lat,lng] with control point at [lat1,lng1]|
|T|([lat,lng])+|quadratic Bézier curve to [lat,lng] with control point at reflection of control point of previous curve [lat1,lng1]|
|Z||close path (line to M)|

Note that only absolute commands (uppercase) are implemented. It's possible to approximate elliptical arcs (command 'A') with Bézier curves (the `elliptical-arc` branch implements this command if you're interested).

For more details on how to use this plugin check the example.
npm package: @jspear/cra-template
Description: The base template for JSpear Create React App.
Latest version: 1.2.0

# cra-template

This is the official base template for [Create React App](https://github.com/facebook/create-react-app).

If you don't specify a template (for example, `--template typescript`), this template will be used by default.

For more information, please refer to:

- [Getting Started](https://create-react-app.dev/docs/getting-started) – How to create a new app.
- [User Guide](https://create-react-app.dev) – How to develop apps bootstrapped with Create React App.
npm package: @jspengine/react-janus-components-lab
Description: Video Room compomnent for react js
Author: Renato Nascimento
Latest version: 1.0.3

# React Janus Components
React components for Janus Plugins including Videoroom

Purpose of this module is to implement the multiple plugins of [Janus](http://janus.conf.meetecho.com) to be used with React apps. The janus.js from the official demo is used as the client library for the moment. This would be converted to a node module at a latter stage.

## Update

npm package had an issue yesterday, fixed now and the example should work

## Supported plugins
1. Videoroom

## Usage

1. Install Janus server, docker image is available at https://hub.docker.com/r/manujith/janus
2. Follow the example for Videoroom
npm package: @jsperf.dev/core
Description: Core API for jsperf.dev ecosystem
Latest version: 0.3.0

# @jsperf.dev/core

## API

### Class: `Benchmark`

Extends: `EventEmitter`

#### `new Benchmark<Context>(options)`

Arguments:

- **options** - `object` - _optional_ - Default: `{}`
  - **warmup** - `boolean` - _optional_ - Default: `true`
  - **samples** - `number` - _optional_ - Default: `10`
  - **meta** - `Meta` - _optional_ - Default: `{}`

#### Instance Properties

##### `Benchmark.context`

- `Context`

A property that will be passed as the first argument to each lifecyle method and run script.

##### `Benchmark.meta`

- `Meta`

A property that represents general information about the benchmark instance. The title is defaulted to `process.argv[1]` (generally the path of the benchmark script).

##### `Benchmark.results`

- `Map<string, Array<PerformanceEntry>>`

This property is updated after the benchmark suite executes.

##### `Benchmark.samples`

- `number`

The number of samples the benchmark suite will run. This property can be modified at any point prior to calling `benchmark.start()`.

##### `Benchmark.warmup`

- `boolean`

When set to `true`, the warmup step will run. This property can be modified at any point prior to calling `benchmark.start()`.

#### Instance Methods

##### `Benchmark.afterAll(func)`

Arguments:

- **func** - `FunctionWithContext<Context>` - _required_

Lifecycle method for adding a function that executes after all other scripts are executed.

##### `Benchmark.afterEach(func)`

Arguments:

- **func** - `FunctionWithContext<Context>` - _required_

Lifecycle method for adding a function that executes after each _run_ script is executed.

##### `Benchmark.beforeAll(func)`

Arguments:

- **func** - `FunctionWithContext<Context>` - _required_

Lifecycle method for adding a function that executes before all scripts are executed.

##### `Benchmark.beforeEach(func)`

Arguments:

- **func** - `FunctionWithContext<Context>` - _required_

Lifecycle method for adding a function that executes before each _run_ script is executed.

##### `Benchmark.run(id, file)`

Arguments:

- **id** - `string` - _required_
- **file** - `string` - _required_

Add a run to the benchmark instance. The `id` must be unique and `file` must be the absolute path to the script.

##### `Benchmark.start()`

Returns: `Promise<void>`

Executes the benchmark suite. Resolves once it completes execution. Does **not** rethrow errors thrown during execution. Errors are emitted through the [`error`](#error) event.

#### Instance Events

##### `start`

Emitted at the beginning of the microtask queued during the constructor. It will not be emitted if no runs have been added.

##### `end`

Emitted at the end of the microtask after all runs have been executed.

##### `error`

Emitted whenever an error is thrown. Will return the thrown error.

```js
const [error] = await once(benchmark, "error");
```

### Type: `FunctionWithContext<Context>`

- `(context: Context, ...extraArgs: unknown[]) => void | Promise<void>`

### Interface: `Meta`

- **title** - `string` - _optional_
- **description** - `string` - _optional_

## Testing

Execute tests using `pnpm test`
npm package: @jsperf.dev/reporter
Description: A reporting plugin for @jsperf.dev/benchmark
Latest version: 0.2.0

# @jsperf.dev/reporter

## Usage

```js
import reporter from "@jsperf.dev/reporter";
import benchmark from "@jsperf.dev/benchmark";

reporter(benchmark, { outDir: "benchmarks" });

benchmark.run("run1", path.resolve(__dirname, "benchmark-run.js"));
```
npm package: @jsphkhan/my-npm-package
Description: My first NPM package
Author: Joseph
Latest version: 2.4.9

# my-npm-package
Test Custom NPM package publish

### Travis Build Badge
[![Build Status](https://travis-ci.org/jsphkhan/my-npm-package.svg?branch=master)](https://travis-ci.org/jsphkhan/my-npm-package)

### TLDR
My simple NPM package that I created to publish on NPM registry
Using Travis CI/CD to auto publish package to NPM registry. 
Whenever Github tag is created, Travis will publish to NPM. 

This is a public NPM package - https://www.npmjs.com/package/@jsphkhan/my-npm-package