open-index/open-npm huggingface dataset:
npm package: @quoeamaster/vuetif
Description: A Vue3 based UI component library with TypeScript support.
Latest version: 0.1.0-e

# Vue 3 + TypeScript + Vite

This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 `<script setup>` SFCs, check out the [script setup docs](https://v3.vuejs.org/api/sfc-script-setup.html#sfc-script-setup) to learn more.

Learn more about the recommended Project Setup and IDE Support in the [Vue Docs TypeScript Guide](https://vuejs.org/guide/typescript/overview.html#project-setup).
npm package: @quoin/eslint-config-quoin
Description: Sharable eslint configs
Author: Hữu Ðà Trần
Latest version: 2.0.2

# quoin/eslint-config-quoin

Shared configuration for [eslint](http://eslint.org/)

## Usage

    npm install --save-dev @quoin/eslint-config-quoin

In your `.eslintrc.json`, use as follow:

    {
      "root": true,
      "extends": "@quoin/eslint-config-quoin"
    }

In your `.eslintrc.test.json`, use as follow:

    {
      "root": true,
      "extends": "@quoin/eslint-config-quoin/node-test"
    }

In your `.eslintrc.client.json`, use as follow:

    {
      "root": true,
      "extends": "@quoin/eslint-config-quoin/client",
      "env": {
        "jquery": true
      }
    }

### grunt-eslint

If you are using `grunt-eslint`, add the same line in your grunt configs.
npm package: @quoin/node-http-with-https
Description: Simple nodejs server with HTTP that redirects to HTTPS
Author: Hữu Ðà Trần
Latest version: 2.0.2

# @quoin/node-http-with-https

[![Build Status](https://travis-ci.com/Quoin/node-http-with-https.svg?branch=master)](https://travis-ci.com/Quoin/node-http-with-https)

This library offers a very simple code to force HTTP traffic to go in HTTPS.

## Usage

    const fs = require('fs');
    const httpWithHttps = require('@quoin/node-http-with-https');

    const behindProxy = false;
    const httpPort = 8080;
    const httpsPort = 8443;
    const httpsOptions = {
      key: fs.readFileSync('/path/to/your/file.key'),
      cert: fs.readFileSync('/path/to/your/file.cert'),
      requestCert: false,
      rejectUnauthorized: false
    };
    const app = express(); // This is your expressJS app.

    const { httpServer, httpsServer } = httpWithHttps(httpsPort, behindProxy, httpsOptions, app);

    httpServer.listen(httpPort, () => console.log(`HTTP on ${httpPort}.`));

    httpsServer.listen(httpsPort, () => console.log(`HTTPS on ${httpsPort}.`));

where:

- `httpsPort`: port that will be used to run the application on HTTPS.
- `behindProxy`: Indicates if the server runs behind a proxy. This will prevent
  `httpsPort` to be appended to the hostname.
- `httpsOptions`: HTTPS options to be passed to `https.createServer()`.
- `app`: the expressJS app to run.


## Example

See fully working [example](./server.js).

To run the example:

    git clone git@github.com:Quoin/node-http-with-https.git
    cd node-http-with-https
    npm install
    npm start

You can then access to:

    http://localhost:8080/
    http://localhost:8080/test/with/path

You should get an error trying any other path, like:

    http://localhost:8080/other

Both should redirect you to the HTTPS path. You will probably have a security
warning because the certificate is self-signed.

See [example/README.md](example/README.md) to see how the self-signed
certificate files were generated.


## LetsEncrypt

This server will have a minimum support for letsencrypt. It will allow the
validation of the acme-challenge in HTTP before redirecting to HTTPS. In order
to do that, it must define the environment variable:

    ACME_CHALLENGE=/some/path/that/is/used/by/certbot
npm package: @quoin/node-rc
Description: Wrapper for rc library.
Author: Hữu Ðà Trần
Latest version: 2.0.1

# @quoin/node-rc

This is a wrapper library for the [rc](https://www.npmjs.com/package/rc) because
it doesn't handle properly scoped modules.

This library apply the same logic as `npm pack` is doing for the name of the
file.

## Usage

    npm install --save @quoin/node-rc

    const rc = require('@quoin/node-rc');
    const packageJson = require('./package.json');
    const config = rc(packageJson.name, {});

You can also add values to be merged after the config file has been loaded:

    const config = rc(packageJson.name, {original: 'value'}, {version: '1.0'});

This would allow `version` not to be overwritten by a value set in the config
file.

This module, unlike the `rc` module, will not mutate neither `baseConfig`, nor
`postConfig`.


## Debugging

This library is using [debug](https://www.npmjs.com/package/debug) with the key
`QI:rc`.
npm package: @quoin/node-test-helpers
Description: Test helpers library for nodeJS
Author: Hữu Ðà Trần
Latest version: 2.0.1

# node-test-helpers

[![Build Status](https://travis-ci.com/Quoin/node-test-helpers.svg?branch=master)](https://travis-ci.com/Quoin/node-test-helpers)

This is an extension of [node-test-helpers-core](https://www.npmjs.com/package/@quoin/node-test-helpers-core) that adds chai plugins for projects.

## To install

To add the library to your project:

    npm install --save-dev @quoin/node-test-helpers

## Usage

An example of usage:

    const testHelpers = require('@quoin/node-test-helpers');

    const moduleToTest = require('./index');

    const expect = testHelpers.expect;

    describe("index", () => {
        it("should export a function with 2 params", () => {
            expect(index).to.be.a('function').to.have.lengthOf(2);
        });
    });

See the [lib/index.js](lib/index.js) file to see what libraries are imported and
refer to their respective documentation.

## Examples

See [node-test-helpers-core's README](https://github.com/Quoin/node-test-helpers-core/blob/master/README.md) for some examples.
npm package: @quoin/node-test-helpers-core
Description: Core test helpers library for nodeJS with Chai plugins
Author: Hữu Ðà Trần
Latest version: 2.0.1

# node-test-helpers-core

[![Build Status](https://travis-ci.com/Quoin/node-test-helpers-core.svg?branch=master)](https://travis-ci.com/Quoin/node-test-helpers-core)

This is a helper library to limit the number of packages to install in your
project. Because of the nature of chai plugins, this library only include the
core for your tests. You will need to write a local helper to include all your
chai plugins,

## To install

To add the library to your project:

    npm install --save-dev @quoin/node-test-helpers-core

## Usage

`local-helper.js`:

    const testHelpers = require('@quoin/node-test-helpers-core');
    const dirtyChai = require('dirty-chai');

    testHelpers.chai.use(dirtyChai);

    module.exports = testHelpers;

`file.unit.test.js`:

    const testHelpers = require('./local-helpers');
    const moduleToTest = require('./index');

    const expect = testHelpers.expect;

    describe("index", () => {
        it("should export a function with 2 params", () => {
            expect(index).to.be.a('function').to.have.lengthOf(2);
        });
    });

See the [lib/index.js](lib/index.js) file to see what libraries are imported and
refer to their respective documentation.

## Examples

### createMocks, createRequest and createResponse

See [node-mocks-http](https://github.com/howardabrams/node-mocks-http) for more
details.

    it("should set headers", () => {
      const {req, res} = testHelpers.createMocks();
    });

### verifyHal

To verify that a portion of a response (or the entire reponse is a valid HAL:

    it("should be a valid HAL", () => {
        const someResponseFromServer = requestCall();
        testHelpers.verifyHal(someResponseFromServer.body);
    });

### verifyProperties

To verify all properties of an object:

    it("should expose known properties", () => {
      const clone = _.clone(moduleToTest);

      testHelpers.verifyProperties(clone, 'string', [
        'prop1',
        'prop2'
      ]);

      testHelpers.verifyProperties(clone, 'function', [
        'prop3',
        'prop4'
      ]);

      expect(clone).to.deep.equal({});
    });
npm package: @quoin/react-test-utils
Description: Quoin's react test utils
Author: Hữu Ðà Trần
Latest version: 1.0.0

# Quoin react test utils

[![Build Status](https://travis-ci.com/Quoin/react-test-utils.svg?branch=master)](https://travis-ci.com/Quoin/react-test-utils)
[![Coverage Status](https://coveralls.io/repos/github/Quoin/react-test-utils/badge.svg?branch=master)](https://coveralls.io/github/Quoin/react-test-utils?branch=master)


Utility library for testing react projects.

It makes sure that [Chai](https://www.chaijs.com/) uses some plugins:

- [chai-immutable](https://www.npmjs.com/package/chai-immutable)
- [dirty-chai](https://www.npmjs.com/package/dirty-chai)

## API

### expect()

See [Chai](https://www.chaijs.com/api/bdd/) `expect`.


### mount()

See [Enzyme's moun()](https://airbnb.io/enzyme/docs/api/mount.html).


### render()

See [Enzyme's render()](https://airbnb.io/enzyme/docs/api/render.html).


### request()


### sandbox()

See [Sinon's sandox()](https://sinonjs.org/releases/latest/).


### shallow()

See [Enzyme's shallow()](https://airbnb.io/enzyme/docs/api/shallow.html).


### spy()

See [Sinon's spy()](https://sinonjs.org/releases/latest/).


### stub()

See [Sinon's stub()](https://sinonjs.org/releases/latest/).


### unexpectedFlow()


### verifyProperties(clone, propertyType, properties)

This function verifies that all the `properties` are defined on the `clone`. It
also deletes the property from the `clone`, making it useful in the following
context.

The `propertyType` are values that would be used in [Chai .to.be.a()](https://www.chaijs.com/api/bdd/#method_a).

```javascript
it(`defines known properties`, () => {
  const clone = { ...someObject };

  verifyProperties(clone, 'string', [
    'aStringProperty',
    'anotherStringProperty'
  ]);

  verifyProperties(clone, 'function', [
    'afunction',
    'anotherFunction'
  ]);

  verifyProperties(clone, 'object', [
    'anObject',
    'anotherObject'
  ]);

  expect(clone).to.be.empty();
});
```
npm package: @quoin/react-utils
Description: Utility functions for React
Author: Hữu Ðà Trần
Latest version: 1.0.17

# Quoin's react utils

[![Build Status](https://travis-ci.com/Quoin/react-utils.svg?branch=master)](https://travis-ci.com/Quoin/react-utils)
[![Coverage Status](https://coveralls.io/repos/github/Quoin/react-utils/badge.svg?branch=master)](https://coveralls.io/github/Quoin/react-utils?branch=master)
[![npm version](https://img.shields.io/npm/v/@quoin/react-utils.svg)](https://www.npmjs.com/package/@quoin/react-utils)


Utility library to use React.


## Warning

The library expects `React` to be global, because it usually comes from an
external lib and not bundled with `webpack`, so the easiest when using on the
server-side is to declare it global inside your start script:

```
# server.js

import React from 'react';

global.React = React;
```


## Usage

- See [How to create a component](component.md)
- See [How to make SSR app](ssr.md)
- See [How to configure React Router](routes-info.md)

## Chrome DevTools

- [React Developer Tools](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi)
- [Redux DevTools](https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd)
npm package: @quoin/react-utils-bs3
Description: Adding displayName to react-bootstrap components
Author: Hữu Ðà Trần
Latest version: 1.0.1

# Quoin React-Utils BS3

This library only intends to add `displayName` to [react-bootstrap@0](https://www.npmjs.com/package/react-bootstrap).

## Usage

```bash
npm i -D @quoin/react-utils-bs3 react-bootstrap@0
```

```javascript
import '@quoin/react-utils-bs3';
```

Now, when you use the React devTool, your component will now have a meaningful
display name.
npm package: @quoin/search-engines
Description: Utility library to validate IP and UA
Latest version: 2.0.1

# Quoin - Search Engines utility library

[![Build Status](https://travis-ci.com/Quoin/node-search-engines.svg?branch=master)](https://travis-ci.com/Quoin/node-search-engines)

This library tries to detect if an access is coming from a search engine.

## Basic usage

    const searchEngines = require('@quoin/search-engines');

    if (searchEngines.match('127.0.0.1', 'Some User Agent')) {
        console.log("This seems to be a search engine.");
    } else {
        console.log("This seems to be a normal visit.");
    }

## API

### `.get(name)`

Gets the search engine defined by `name`. It returns an instance of
`SearchEngine`.

### `.listNames()`

Gets the list of search engine names. The names can then be used with
`.get(name)` call to get the specific search engine instance.

### `.match(ipAddress, userAgentString)`

Finds if the combination of `ipAddress` and `userAgentString` refers to a known
search engine. It returns `true` or `false`.

### `.find(ipAddress, userAgentString)`

Finds the first search engine instance that matches the combination. The
instance of `SearchEngine` is returned.


## Where are the information coming from?

This is a mixed list of manually massaged information from below sites:

- The list of CIDR comes from
  [Free IP2Location Firewall List by Search Engine](https://www.ip2location.com/free/robot-whitelist)

  I've obtained the `Apache .htaccess allow` file format and hand edited them to
  only have the CIDR on each line.

- The user-agent data comes from
  (https://www.rtcx.net/bot-list)[https://www.rtcx.net/bot-list]

  Only `Search Engine` are keep for this repo. Some CIDR not present on above
  source are added from here.
npm package: @quoine/components
Description: Quoine common components like Input, Modal, Money, ... for Quoine Trade, Quoine Accounts, Quoine Lending.
Author: Huong Hk
Latest version: 1.0.9

# Quoine Components

Module to share common components like Input, Modal, Money, ... for Quoine Trade, Quoine Accounts, Quoine Lending.

## Installation

```sh
$ npm install --save @quoine/components
```

## Usage

```js
import { Input, ButtonWLoading as Button } from '@quoine/components';
```
## License

MIT © [Huong Hk]()
npm package: @quoine/core-components
Description: Quoine common components like Input, Modal, Money, ... for Quoine Trade, Quoine Accounts, Quoine Lending.
Author: Huong Hk
Latest version: 1.3.3

# Quoine Core Components

Module to share core components like Input, Modal, Money, ... for Quoine Trade, Quoine Accounts, Quoine Lending.

## Installation

```sh
$ npm install --save @quoine/core-components
```

## Usage

```js
import { Input } from '@quoine/core-components';
```
## License

MIT © [Huong Hk]()
npm package: @quoine/intl
Description: Quoine intl
Author: Huong Hk
Latest version: 0.0.2

# quoine-intl [![NPM version][npm-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Dependency Status][daviddm-image]][daviddm-url] [![Coverage percentage][coveralls-image]][coveralls-url]
> Quoine intl

## Installation

```sh
$ npm install --save quoine-intl
```

## Usage

```js
var quoineIntl = require('quoine-intl');

quoineIntl('Rainbow');
```
## License

MIT © [Huong Hk]()


[npm-image]: https://badge.fury.io/js/quoine-intl.svg
[npm-url]: https://npmjs.org/package/quoine-intl
[travis-image]: https://travis-ci.org/QuoineFinancial/quoine-intl.svg?branch=master
[travis-url]: https://travis-ci.org/QuoineFinancial/quoine-intl
[daviddm-image]: https://david-dm.org/QuoineFinancial/quoine-intl.svg?theme=shields.io
[daviddm-url]: https://david-dm.org/QuoineFinancial/quoine-intl
[coveralls-image]: https://coveralls.io/repos/QuoineFinancial/quoine-intl/badge.svg
[coveralls-url]: https://coveralls.io/r/QuoineFinancial/quoine-intl
npm package: @quoine/object-to-formdata
Description: A convenient JavaScript function that converts an object to a FormData instance
Author: Quoine
Latest version: 0.0.1

# object-to-formdata
A convenient JavaScript function that converts an object to a FormData instance

```js
const objectToFormData = require('object-to-formdata')

const object = {
  /**
   * key-value mapping
   * values can be primitives or objects
   */
}

const formData = objectToFormData(object)

console.log(formData)
```
npm package: @quoine/react-popover
Description: A specification backed popover for react
Author: Jason Kuhrt
Latest version: 0.4.24

:toc: macro
:toc-title:
:toclevels: 99

# react-popover

image:https://travis-ci.org/littlebits/react-popover.svg?branch=master["Build Status", link="https://travis-ci.org/littlebits/react-popover"]


toc::[]



## Installation

```
npm install --save react-popover
```



## Demos

* link:https://littlebits.github.io/react-popover/build/playground.html[Playground]
* link:https://littlebits.github.io/react-popover/build/rows.html[Rows]
* link:https://littlebits.github.io/react-popover/build/jsx.html[Using JSX]

To run demos locally execute `npm start`. If you do not see logs in the console refresh the browser once (https://github.com/littlebits/react-popover/issues/35).



## API

### `export default` `Popover(props, target)`

#### `props :: {...}`

---

##### `body :: Node | Array Node`
The `popover` content. Content is rooted (becomes children of) `.Popover-body` and thus `body` can be a single `node` _or an array of `nodes`_.

---

##### `isOpen :: Boolean`
Determines Whether or not the popover is rendered.

---

##### `preferPlace :: Enum String | Null`
Sets a ***preference*** of where to position the Popover. Only useful to specify placement in case of multiple available fits. Defaults to `null`. Valid values are:

`above | right | below | left` :: Prefer an explicit side.
`row | column` :: Prefer an orientation.
`start | end` :: Prefer an order.
`null` :: No preference, automatic resolution. This is the default.

---

##### `place :: String | Null`
Like `preferPlace` except that the given place is a ***requirement***. The resolver becomes scoped or disabled. It is scoped if the `place` is an `orientation` or `order` but disabled if it is a `side`. For example `place: "row"` scopes the resolver to `above` or `below` placement but `place: "above"` removes any need for the resolver.

---

##### `onOuterAction :: (Event) -> Void`
A callback function executed every time the user does an action (`mousedown` or `touchstart`) outside the DOM tree of both `Popover` and `Target`. A canonical use-case is to automatically close the Popover on any external user action.

---

##### `refreshIntervalMs :: Number | Falsey`
The polling speed (AKA time between each poll) in milliseconds for checking if a layout refresh is required. This polling is required because it is the only robust way to track the position of a target in the DOM. Defaults to `200`. Set to a falsey value to disable.

---

#### `enterExitTransitionDurationMs :: Number | Falsey`
The amount of time in milliseconds that it takes to complete the enter and exit animation. Defaults to '500'.

---

#### `tipSize :: Number`
Defines the size of the tip pointer.  Use .01 to disable tip.  Defaults to '7'.

---

##### Standard

* Properties like `className` and `style`.


---

#### `target :: React Element`

- The React Element that this popover will orient itself around. `target` `rendering tree` is unaffected. `Popover` _will_ become its `owner`.
npm package: @quoine/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.0.22

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebook/create-react-app).<br>
Please refer to its documentation:

- [Getting Started](https://facebook.github.io/create-react-app/docs/getting-started) – How to create a new app.
- [User Guide](https://facebook.github.io/create-react-app/) – How to develop apps bootstrapped with Create React App.
npm package: @quoine/translate
Description: Quoine Translate for Landing Page
Author: Eugene Nikitin
Latest version: 0.0.1

# [DEPRECATED]
In favour of [modern-package-boilerplate](https://github.com/eunikitin/modern-package-boilerplate)

[![Build Status](https://travis-ci.org/eunikitin/npm-package-es6-boilerplate.svg?branch=master)](https://travis-ci.org/eunikitin/npm-package-es6-boilerplate)
[![Coverage Status](https://coveralls.io/repos/github/eunikitin/npm-package-es6-boilerplate/badge.svg?branch=master)](https://coveralls.io/github/eunikitin/npm-package-es6-boilerplate?branch=master)
[![dependencies Status](https://david-dm.org/eunikitin/npm-package-es6-boilerplate/status.svg)](https://david-dm.org/eunikitin/npm-package-es6-boilerplate)
[![devDependencies Status](https://david-dm.org/eunikitin/npm-package-es6-boilerplate/dev-status.svg)](https://david-dm.org/eunikitin/npm-package-es6-boilerplate?type=dev)

## Features
* Build with [webpack 2](https://webpack.js.org/) and [babel](https://babeljs.io/)
* Test with [mocha](https://mochajs.org/), [chai](http://chaijs.com/) and [sinon](http://sinonjs.org/)
* Cover with [istanbul](https://github.com/gotwarlost/istanbul)
* Lint with [eslint](http://eslint.org/) ([air-bnb config](https://github.com/airbnb/javascript))
* CI with [travis-ci.org](https://travis-ci.org/)
* Coverage info with [coveralls.io](https://coveralls.io)

## Getting started
1. [Clone this repo from github](https://github.com/eunikitin/npm-package-es6-boilerplate)
2. Inside repo directory run `npm install && rm -r .git && git init`
2. Update package.json with your information

## Usage
### Commands

#### `npm run clean`
Delete all cache and output files

#### `npm run dev`
Build your library in development mode

#### `npm run build`
Build your library in production mode

#### `npm run test`
Run tests

#### `npm run test:watch`
Run tests in watch mode

#### `npm run cover`
Cover your code (Work with ES6)

#### `npm run coveralls`
Sends coverage details to [coveralls.io](https://coveralls.io).
Used in .travis.yml and should not be used manually.

#### `npm run lint`
Check your code for errors and code styles

#### `npm run prepublish`
Hook for npm, that executes when you publishing package in npm repository.

### Lint
This boilerplate uses
[air-bnb code style conventions](https://github.com/airbnb/javascript#table-of-contents),
however if you don't like it, you can disable it, by removing the following line in 
`.eslintrc` config file:
```js
{
  //...
  
  "extends": "airbnb"
}
```

### Webpack aliases
If you are as tired as me to write '../../../' in the
require statements, you can use
[alias feature provided by webpack](https://webpack.js.org/configuration/resolve/#resolve-alias).
Here is an example of aliases, built in this boilerplate
by default (`builder/resolve.js`):
```js
resolve: {
    alias: {
        Src: path.resolve(process.cwd() + '/src'),
        Lib: path.resolve(process.cwd() + '/lib')
    }
}
```
Feel free to add your custom aliases, they are awesome.
npm package: @quokka-ui/table
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Author: Janith Madarasinghe
Latest version: 0.0.4

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

- Configure the top-level `parserOptions` property like this:

```js
export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})
```

- Replace `tseslint.configs.recommended` to `tseslint.configs.recommendedTypeChecked` or `tseslint.configs.strictTypeChecked`
- Optionally add `...tseslint.configs.stylisticTypeChecked`
- Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and update the config:

```js
// eslint.config.js
import react from 'eslint-plugin-react'

export default tseslint.config({
  // Set the react version
  settings: { react: { version: '18.3' } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs['jsx-runtime'].rules,
  },
})
```
npm package: @quonfig/node
Description: Quonfig SDK for Node.js - Feature Flags, Live Config, and Dynamic Log Levels
Author: Quonfig
Latest version: 0.0.6

# @quonfig/node

Node.js SDK for [Quonfig](https://quonfig.com) — Feature Flags, Live Config, and Dynamic Log Levels.

> **Note:** This SDK is pre-1.0 and the API is not yet stable.

## Installation

```bash
npm install @quonfig/node
```

## Quick Start

```typescript
import { Quonfig } from "@quonfig/node";

const quonfig = new Quonfig({ sdkKey: "your-sdk-key" });
await quonfig.init();

// Feature flags
if (quonfig.isFeatureEnabled("new-dashboard")) {
  // show new dashboard
}

// Config values
const limit = quonfig.getNumber("rate-limit");
const regions = quonfig.getStringList("allowed-regions");

// Context-aware evaluation
const value = quonfig.get("homepage-hero", {
  user: { key: "user-123", country: "US" },
});

// Bound context for repeated lookups
const userClient = quonfig.inContext({
  user: { key: "user-123", plan: "pro" },
});
userClient.get("feature-x");
userClient.isFeatureEnabled("beta-feature");

// Clean up when done
quonfig.close();
```

## Options

```typescript
new Quonfig({
  sdkKey: "your-sdk-key",       // Required
  apiUrl: "https://api.quonfig.com", // API endpoint (default)
  enableSSE: true,               // Real-time updates via SSE (default: true)
  enablePolling: false,          // Polling fallback (default: false)
  pollInterval: 60000,           // Polling interval in ms (default: 60000)
  initTimeout: 10000,            // Init timeout in ms (default: 10000)
  onNoDefault: "error",          // "error" | "warn" | "ignore" (default: "error")
  globalContext: { ... },        // Context applied to all evaluations
  datadir: "./workspace-data",   // Load local workspace directories instead of API
  datafile: "./config.json",     // Legacy local envelope path
});
```

## License

MIT
npm package: @quonset/minim
Description: MNX notation renderer
Author: Barret Anspach
Latest version: 0.0.8

# minim

A React.js component for rendering music encoded with MNX. Still a work-in-progress!

## Peer requirements

Minim (as of v0.0.7) works with React 19.2.3 or above, and Node 20+.

Ideally the package will in the future work within any Javascript environment; I'm considering creating a web component version, &c.

## How to use

Add `@quonset/minim` as a dependency to your project:

```bash
npm i @quonset/minim --save
```

Import `@quonset/minim` into your project, import a valid [MNX](https://w3c.github.io/mnx/docs/) document (saved with a `.json` extension), and pass the document to Minim:

```js
import Minim from '@quonset/minim';
import myFirstComposition from '@/path/to/my-first-composition.json';
...

export default function Component() {
  return (
    <div>
      <Minim score={myFirstComposition} />
    </div>
  )
}
```

Note: As of v0.0.7, There are some differences between what I've implemented and the MNX spec — mainly to deal with outlier "modern" notational systems (such as allowing for multiple concurrent tempi and/or meters). Down the road, I hope to allow a consumer of Minim to render "CWMN" (i.e. canonical MNX) notation, as well as "extended" (i.e. polytemporal, etc.) notation.

An open question, too, is whether or not MNX documents can be nested. More on this in subsequent releases.

## Documentation

TBD. At the moment, this package is under slow but active development. Hoping to get there with some minimal (and much needed) documentation, partly to be sure development continues along a productive trajectory.

## Contributing

### Publishing new versions

1. Create a PR of the work, with

- the version number already incremented, and
- a CHANGELOG entry describing the work you did.

2. When that PR is merged into `master`, and while on `master`, run: `npm publish --access public`

- Follow semantic versioning (0.0.1 for feature fixes/bugs, 0.1.0 for new features that are backward-compatible, and 1.0.0 for new features that break backward-compatibility).
npm package: @quorak/fullcalendar-react
Description: An official FullCalendar component for React
Latest version: 5.9.1


# FullCalendar React Component [![Build Status](https://travis-ci.com/fullcalendar/fullcalendar-react.svg?branch=master)](https://travis-ci.com/fullcalendar/fullcalendar-react)

An official FullCalendar component for React.

This is more than a mere "connector". It tells the core FullCalendar package to begin rendering with **React** virtual DOM nodes as opposed to the [Preact](https://preactjs.com/) nodes it normally uses, transforming FullCalendar into a "real" React component. You can learn a bit more [from this blog post](https://fullcalendar.io/blog/2020/05/react-ts-v5-beta) (more info to come).

- [FullCalendar React Component Docs](https://fullcalendar.io/docs/react)
- [Example Project](https://github.com/fullcalendar/fullcalendar-example-projects/tree/master/react)
- [Example Project with TypeScript](https://github.com/fullcalendar/fullcalendar-example-projects/tree/master/react-typescript)
- [Contributor Guide](CONTRIBUTORS.md)
npm package: @quority/activity
Description: <div align="center">
Author: bitomic
Latest version: 1.1.2

<div align="center">

![Logo](https://avatars.githubusercontent.com/u/126923974?s=200&v=4)

[![GitHub](https://img.shields.io/github/license/quority/fandom)](https://github.com/quority/fandom/blob/main/LICENSE.md)
[![npm](https://img.shields.io/npm/v/@quority/fandom?color=crimson&logo=npm&style=flat-square)](https://www.npmjs.com/package/@quority/fandom)
</div>

---