open-index/open-npm huggingface dataset:
npm package: @lypt1x/neu
Description: neu CLI for Neutralinojs
Author: Neutralinojs and contributors
Latest version: 11.5.1

<div align="center"><img src="images/logo.png"/></div>

[![GitHub release (latest by date)](https://img.shields.io/github/v/release/neutralinojs/neutralinojs-cli)](https://github.com/neutralinojs/neutralinojs-cli/releases)
![npm](https://img.shields.io/npm/v/@neutralinojs/neu)
![npm](https://img.shields.io/npm/dt/@neutralinojs/neu)
[![GitHub last commit](https://img.shields.io/github/last-commit/neutralinojs/neutralinojs-cli.svg)](https://github.com/neutralinojs/neutralinojs-cli/commits/main)
![Build status](https://github.com/neutralinojs/neutralinojs-cli/actions/workflows/test_suite.yml/badge.svg)

The official CLI of Neutralinojs. See neu CLI [documentation](https://neutralino.js.org/docs/cli/neu-cli/) for more details. Release notes are available at [this page](https://neutralino.js.org/docs/release-notes/cli).

```bash
npm i -g @neutralinojs/neu
```
### Requirements

- Node.js v12 or later version.
- npm, yarn, or any Node.js package manager.

### License

[MIT](LICENSE)

### Contributing to Neutralinojs

We really appreciate your code contributions. Please read [this contribution guide](https://neutralino.js.org/docs/contributing/framework-developer-guide#contribution-guidelines) before sending a pull request. Thank you for your contributions.

#### ⚠️ Notice for contributors
Please note that we would like to keep this project's dependencies list minimal as possible. Make sure that you don't add new dependencies (external `npm` modules) with your pull requests. Also, don't use latest Node/JavaScript features that won't work on older Node.js versions. Thank you :tada:

### Contributors

<a href="https://github.com/neutralinojs/neutralinojs-cli/graphs/contributors">
  <img src="https://contrib.rocks/image?repo=neutralinojs/neutralinojs-cli" />
</a>

Made with [contributors-img](https://contrib.rocks).
npm package: @lyq01/materials-test
Description: cs-materials
Author: fusion-team
Latest version: 1.1.1

# cs-materials

一个面向 PC 的业务组件库

## 调试
启动调试

```shell
npm run lowcode:dev             # 打开开发环境，运行所有组件
yarn lowcode:dev 
```

构建

```shell
npm run lowcode:build
yarn lowcode:build 
```

### 发布npm公共包
```shell
npm publish --access public
```
npm package: @lyqluis/kimi-chat-cli
Description: Personal terminal-based chat client for Kimi AI
Latest version: 0.1.3

# kimi-chat-cli

A personal terminal-based chat client for Kimi AI, built with React and Ink.

## Overview

A personal project I built for my own use — because I don't want to frequently open a browser or switch tabs for trivial questions, as my slow computer handles that poorly. It provides a terminal UI with streaming responses, chat history management, and some customization options.

## Features

- **Real-time Streaming**: Messages stream in real-time with a typing effect
- **Chat History**: View, search, and manage your previous conversations
- **Model select**:
  - `Ctrl+p` - Open selector
  - `↑/↓` or `j/k` - Navigate in the list
  - `Enter` - Select model
- **Toggle Modes**:
  - Web Search: `Ctrl+w`
  - Long Thinking: `Ctrl+l`
- **Commands**: `/history`, `/new`, `/clear`, `/exit`, `/help`...(some not yet implemented)
- **Keyboard Navigation**:
  - `Enter` - Send message / Load selected chat from history
  - `Esc` - Cancel / Return to chat
  - `Space` - Expand chat preview in history
  - `M` - Load more history items
  - `D` - Delete chat from history
  - `↑/↓` or `j/k` - Navigate in history list
  - `Ctrl+C` - Exit application

## Installation

```bash
# Build from source
pnpm build

# Install globally (optional)
npm install -g .
```

## Configuration

Before using, you need to configure your web Kimi AI token.

1. Get your token from browser:

   - Open [kimi.ai](https://kimi.ai) in your browser
   - Open DevTools (F12) → Application/Storage → Cookies
   - Copy the value of `kimi-auth` or similar auth token

2. Create config file:

```bash
mkdir -p ~/.kimi-chat-cli
echo 'APP_TOKEN="YOUR_TOKEN_HERE"' > ~/.kimi-chat-cli/chatclirc
```

## Usage

```bash
# Run the CLI
kimi-chat

# Check Version
kimi-chat --version
```

## Development

```bash
# Watch mode with auto-restart
pnpm dev

# Watch with nodemon
pnpm dev-nodemon

# Run tests
pnpm test
```

## Tech Stack

- [React](https://react.dev/) - UI library
- [Ink](https://github.com/vadimdemedes/ink) - React for terminals
- [TypeScript](https://www.typescriptlang.org/) - Type safety
- [Vitest](https://vitest.dev/) - Testing framework

## License

MIT
npm package: @lyra-network/eslint-config-react
Description: Lyra's ESLint config for React apps
Author: Lyra
Latest version: 2.2.0
Deprecated: This package is no longer maintained, please use @lyracom/eslint-config-react instead.

# @lyra-network/eslint-config-react

> Lyra's ESLint config for React apps

[![npm (scoped)](https://img.shields.io/npm/v/@lyra-network/eslint-config-react)](https://www.npmjs.com/package/@lyra-network/eslint-config-react)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) », please follow instructions from this repo.
npm package: @lyra-network/prettier-config
Description: Lyra's Prettier config
Author: Lyra
Latest version: 1.0.4
Deprecated: This package is no longer maintained, please use @lyracom/prettier-config instead.

# @lyra-network/prettier-config

> Lyra's Prettier config

[![npm (scoped)](https://img.shields.io/npm/v/@lyra-network/prettier-config)](https://www.npmjs.com/package/@lyra-network/prettier-config)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) », please follow instructions from this repo.
npm package: @lyra-theme/tokens
Description: An opinionated color theme for muted and smooth visual experience
Author: Kawasaki Shizuku
Latest version: 0.1.7

# Lyra Color Tokens

This package is a color library for Lyra Theme, you can simply use it to access Lyra's colors and keep them in sync with the source via NPM.

## Usage

To access Lyra colors, we recommend using named access, for example:

``` javascript
import lyra from "@lyra-theme/tokens"

// e.g. access normal blue color
const blue = lyra.normal.blue

// e.g. access bright green color
const green = lyra.bright.blue

// e.g. access ANSI normal red color
const ansiRed = lyra.ansi.normal.red

// e.g. access Ecosystem Background color
const background = lyra.eco.background

```

Otherwise, you can also use the token number to access, for example:

``` javascript
import lyra from "@lyra-theme/tokens"

// e.g. access Lyra 1 color
const blue = lyra.base.lyra1

// e.g. access ANSI 7 color
const ansiRed = lyra.ansi.base.ansi7

```

Note that Lyra Colors' numbering logic is the same as ANSI, and in the current version, they point to the exact same colors. The use of different keys is to make the distinction explicit and for possible future ANSI-specific modifications.

Made by Kawasaki Shizuku
npm package: @lyra/check
Description: Lyra check Lyra plugins and projects
Author: Vega
Latest version: 0.3.0

# @lyra/check

Lyra check Lyra plugins and projects. Useful in pre-publish hooks.

## Installing

```
npm install -g @lyra/check
```

## Usage

```
Usage: lyra-check [DIRECTORY]
Lyra check Lyra plugins and projects.

-p, --production  check production (compiled) paths
-v, --version     output version information and exit
-h, --help        display this help and exit

With no DIRECTORY, checks current directory.
```

## License

MIT-licensed. See LICENSE.
npm package: @lyra/code-input
Description: Ace editor for editing code
Author: Vega
Latest version: 0.3.0

# code-editor

Ace editor for editing code.

Use `type: text` and `options.editor = 'code'`

## In schema

```
import code from 'part:@lyra/form-builder/input/code/schema'

{
  name: 'myCode',
  title: 'Code editor (default)',
  description: 'Code editor',
  type: 'code'
}
```
npm package: @lyra/color-input
Description: Color input
Author: Vega
Latest version: 0.3.0

# @lyra/color-input

Color input for [Lyra](https://vegapublish.com/) that stores selected colors in hex, hsl, hsv and rgb format.

## Installation

```
lyra install @lyra/color-input
```

## Usage

Use it in your schema types:

```js
// [...]
{
  fields: [
    // [...]
    {
      name: 'favoriteColor',
      title: 'Favorite color',
      type: 'color'
    }
  ]
}
```

Note that the above only works if you import and use the `all:part:@lyra/base/schema-type` part in your schema. If you do _not_ import this part to your schema, you can import the color schema from `part:@lyra/color-input/schema`.

## Options

To disable the alpha option, set `disableAlpha` to `true`:

```js
// ...fields...
{
  name: 'favoriteColor',
  title: 'Favorite color',
  type: 'color',
  options: {
    disableAlpha: true
  }
}
```

## Data model

```js
{
  _type: 'color',
  hex: '#29158a',
  alpha: 0.9,
  hsl: {
    h: 249.99999999999994,
    s: 0.7328000000000001,
    l: 0.313,
    a: 0.9
  },
  hsv: {
    h:249.99999999999994,
    s: 0.8457987072945522,
    v: 0.5423664,
    a: 0.9
  },
  rgb: {
    r: 41
    g: 21,
    b: 138,
    a: 0.9
  }
}
```

## License

MIT-licensed. See LICENSE.
npm package: @lyra/default-login
Description: Lets the user log in to Lyra.
Author: Vega
Latest version: 0.3.0

# @lyra/default-login

Let a user log into Lyra, and get access to the child content.

## Configuration

By default this component will ask the Lyra API and get a list of providers, which the user can login with.

However it is possible for enterprise customers to supply their own third party authentication server as a provider as well.

This is done through configuring the studio with the file `./config/@lyra/default-login.json`

Example:

```
{
  providers: {

    // Append the custom providers to the default providers or replace them.
    "mode": "append", // default - or 'replace'

    // If true, don't show the choose provider logo screen,
    // automatically redirect to the single provider login
    "redirectOnSingle": false // default

    // The custom provider implementations
    "entries": [
      {
        "name": "vandelay",
        "title": "Vandelay Industries",
        "url": "https://api.vandelay.industries/login",
        "logo": "/static/img/vandelay.svg" // Optional, put it in the studio static folder
      }
    ]
  }
}
```

## Using the component

```
<LoginWrapper>
  {user => <Layout><div>{user.name} is logged in!</div></Layout>}
</LoginWrapper>
```

### Props

```
static propTypes = {
  children: PropTypes.oneOfType([
    PropTypes.node,
    PropTypes.func
  ]).isRequired,
  title: PropTypes.string,
  description: PropTypes.string,
  LyraLogo: PropTypes.func
}
```

```
static defaultProps = {
  title: 'Choose login provider',
  description: null,
  LyraLogo: LyraStudioLogo,
}
```
npm package: @lyra/document-store
Description: Lyra / saga document store
Author: Vega
Latest version: 0.3.0

# Document store

Lyra / saga document store

## Example

```js
// If you are interested in everything that happens with document `lol42`
const subscription = documents.byId('lol42').subscribe(event => {
  console.log('Something happened with document lol42!', event)
})

// After a while, when you are no longer interested in updates fom document `lol42`:
subscription.unsubscribe()
```

## How it works

When you add a subscriber to a document the first thing that happens is that the subscriber function is called with a snapshot of the document's current state. This happens as soon as the snapshot is retrieved. If there is a cached version of it on the client, the snapshot is received immediately (synchronously).

From that moment on, you will receive a new event every time something happens to the document, until you unsubscribe again.

## API

- `createDocumentStore({serverConnection: ServerConnection}) : DocumentStore`

ServerConnection must be an object with the following api:

- `byId(id : string) : Observable<DocumentEvent>`
- `query(query : string) : Observable<QueryResultEvent>`
  (todo, add more)

### DocumentStore

### Query methods

- `byId(id : string) : Observable<DocumentEvent>`
- `byIds(ids : Array<string>) : Observable<QueryResultEvent>`
- `query(query : string) : Observable<QueryResultEvent>`

### Mutation methods

- `update(id : string, spec : UpdateSpec) : Observable<OperationEvent>`
- `create(document : Document) : Observable<OperationEvent>`
- `replace(documentId : string, document : Document) : Observable<OperationEvent>`
- `createOrReplace(document : Document) : Observable<OperationEvent>`
- `delete(documentId : string) : : Observable<OperationEvent>`

### Document

- `_id : string`
- `_type : string`

### DocumentEventType

### DocumentEvent

- `type : string` either one of `snapshot`, `update`
- `snapshot : Document`
npm package: @lyra/export
Description: Export Lyra documents and assets
Author: Vega
Latest version: 0.3.0

# @lyra/export

Exports documents and assets from a Lyra dataset

## Installing

```
npm install --save @lyra/export
```

## Usage

```js
const exportDataset = require('@lyra/export')

exportDataset({
  // Instance of @lyra/client configured to correct project ID and dataset
  client: someInstantiatedLyraClientInstance,

  // Name of dataset to export
  dataset: 'myDataset',

  // Path to write zip-file to, or `-` for stdout
  outputPath: '/home/your-user/myDataset.zip',

  // Whether or not to export assets. Note that this operation is currently slightly lossy;
  // metadata stored on the asset document itself (original filename, for instance) might be lost
  // Default: `true`
  assets: false,

  // Exports documents only, without downloading or rewriting asset references
  // Default: `false`
  raw: true,

  // Whether or not to export drafts
  // Default: `true`
  drafts: true,

  // Export only given document types (`_type`)
  // Optional, default: all types
  types: ['products', 'shops']
})
```

## Future improvements

- Restore original filenames, keep track of duplicates, increase counter (`filename (<num>).ext`)
- Skip archiving on raw/no-asset mode?

## CLI-tool

This functionality is built in to the `@lyra/cli` package as `lyra dataset export`

## License

MIT-licensed. See LICENSE.
npm package: @lyra/generate-help-url
Description: Generates URLs to specific sections of the Lyra documentation
Author: Vega
Latest version: 0.3.0

# help-url

Generates URLs to specific sections of the Lyra documentation

## Usage

```
generateHelpUrl('form-builder-input-missing-required-prop')
```

Generate a help URL that points to a help document with the id `form-builder-input-missing-required-prop`.

You can create the document with the id by adding ID to the studio /edit link.
npm package: @lyra/google-maps-input
Description: Lyra plugin providing input handlers for geo-related input types using Google Maps
Author: Vega
Latest version: 0.3.0

# @lyra/google-maps-input

Lyra plugin providing input handlers for geo-related input types using Google Maps

## Example app

First write a valid Google Maps API key into `./example/config/@lyra/google-maps-input.json`

Then `npm start`
npm package: @lyra/imagetool
Description: The image hotspot selector / cropper used in Lyra
Author: Vega
Latest version: 0.3.0

# The image tool used in lyra

## Getting started

    npm install --save @lyra/imagetool

## Usage

### ImageTool widget

```js
import React from 'react'
import ImageTool from '@lyra/imagetool'

class MyComponent extends React.Component {
  state = {
    value: {
      hotspot: {
        x: 0.4,
        y: 0.3,
        height: 0.6,
        width: 0.4
      },
      crop: {
        left: 0.1,
        right: 0.2,
        top: 0.1,
        bottom: 0.21
      }
    }
  }

  handleImageToolchange = newValue => {
    this.setState({value: newValue})
  }

  render() {
    return (
      <ImageTool
        src="https://c4.staticflickr.com/8/7514/16189387096_420dbca030_h.jpg"
        value={this.state.value}
        onChange={handleImageToolchange}
      />
    )
  }
}
```

## Usage

### CSS style calculator

```js
import calculateStyles from '@lyra/imagetool/calculateStyles'

const styles = calculateStyles({
  hotspot: {
    x: 0.4,
    y: 0.3,
    height: 0.6,
    width: 0.4
  },
  crop: {
    left: 0.1,
    right: 0.2,
    top: 0.1,
    bottom: 0.21
  },
  image: {height: 100, width: 125},
  container: {aspectRatio: 16 / 10},
  align: {
    x: 'left',
    y: 'center'
  }
})
```

returns an object with style objects that can be used with markup

```json
{
  "container": {
    "overflow": "hidden",
    "position": "relative",
    "width": "100%",
    "height": "62.5%"
  },
  "crop": {
    "position": "absolute",
    "overflow": "hidden",
    "height": "100%",
    "width": "79.26%",
    "top": "7.97%",
    "left": "17.51%"
  },
  "image": {
    "position": "absolute",
    "height": "144.93%",
    "width": "142.86%",
    "top": "-14.49%",
    "left": "-14.29%"
  },
  "padding": {
    "marginTop": "62.5%"
  }
}
```

this can then be passed to jsx markup with the following structure:

```jsx
<div style={styles.container}>
  <div style={styles.padding} />
  <div style={styles.crop}>
    <img
      src="https://c4.staticflickr.com/8/7514/16189387096_420dbca030_h.jpg"
      style={styles.image}
    />
  </div>
</div>
```
npm package: @lyra/import
Description: Import documents to a Lyra dataset
Author: Vega
Latest version: 0.3.0

# @lyra/import

Imports documents from an [ndjson](http://ndjson.org/)-stream to a Lyra dataset

## Installing

```
npm install --save @lyra/import
```

## Usage

```js
const fs = require('fs')
const lyraClient = require('@lyra/client')
const lyraImport = require('@lyra/import')

const client = lyraClient({
  apiHost: '<the lyra api host>',
  dataset: '<your target dataset>',
  token: '<token-with-write-perms>',
  useCdn: false
})

// Input can either be a readable stream (for a `.tar.gz` or `.ndjson` file), a folder location (string), or an array of documents
const input = fs.createReadStream('my-documents.ndjson')
lyraImport(input, {
  client: client,
  operation: 'create' // `create`, `createOrReplace` or `createIfNotExists`
})
  .then(numDocs => {
    console.log('Imported %d documents', numDocs)
  })
  .catch(err => {
    console.error('Import failed: %s', err.message)
  })
```

## CLI-tool

This functionality is built in to the `@lyra/cli` package as well as a standalone [@lyra/import-cli](https://www.npmjs.com/package/@lyra/import-cli) package.

## Future improvements

- When documents are imported, record which IDs are actually touched
  - Only upload assets for documents that are still within that window
  - Only strengthen references for documents that are within that window
  - Only count number of imported documents from within that window
- Asset uploads and strengthening can be done in parallel, but we need a way to cancel the operations if one of the operations fail
- Introduce retrying of asset uploads based on hash + indexing delay
- Validate that dataset exists upon start
- Reference verification
  - Create a set of all document IDs in import file
  - Create a set of all document IDs in references
  - Create a set of referenced ID that do not exist locally
  - Batch-wise, check if documents with missing IDs exist remotely
  - When all missing IDs have been cross-checked with the remote API
    (or a max of say 100 items have been found missing), reject with
    useful error message.

## License

MIT-licensed. See LICENSE.
npm package: @lyra/import-cli
Description: CLI tool that imports documents from an ndjson file or URL
Author: Vega
Latest version: 0.3.0

# @lyra/import-cli

CLI tool that imports documents from an ndjson file or URL

## Installation

```
npm install -g @lyra/import-cli
```

## Usage

```
  CLI tool that imports documents from an ndjson file or URL

  Usage
    $ lyra-import -a <api host> -d <dataset> -t <token> sourceFile.ndjson

  Options
    -a, --api <api host> API host of lyra backend
    -d, --dataset <dataset> Dataset to import to
    -t, --token <token> Token to authenticate with
    --replace Replace documents with the same IDs
    --missing Skip documents that already exist
    --help Show this help

  Examples
    # Import "./my-dataset.ndjson" into dataset "staging"
    $ lyra-import -p myPrOj -d staging -t someSecretToken my-dataset.ndjson

    # Import into dataset "test" from stdin, read token from env var
    $ cat my-dataset.ndjson | lyra-import -p myPrOj -d test -

  Environment variables (fallbacks for missing flags)
    --token = LYRA_IMPORT_TOKEN
```

## License

MIT-licensed. See LICENSE.
npm package: @lyra/mutator
Description: A set of models to make it easier to utilize the powerful real time collaborative features of Lyra
Author: Vega
Latest version: 0.3.0

## @lyra/mutator

[![Build Status](https://travis-ci.org/lyra-io/mutator.svg?branch=master)](https://travis-ci.org/lyra-io/mutator)

## Features

- Lyra flavored jsonpath matching engine with flexible interface that plays
  well with React
- An implementation of the mutation operations of Lyra that can be applied to
  vanilla javascript objects, or through a flexible interface: any weird
  document representation you may require
- TODO: A model to track documents as they are mutated both locally and remotely
  through the real time query feature of Lyra
- Note: If `patch.id` doesn't match `document._id`, the patch will be ignored
  during `apply`.

## Usage

```javascript
import {Patcher} from '@lyra/mutator'

const document = {
  _id: 'a1b2c3',
  a: {}
}

const patcher = new Patcher({
  id: 'a1b2c3',
  set: {
    'a.b': 'My new value'
  }
})

console.log(patcher.apply(document))

=> {
  _id: 'a1b2c3',
  a: {
    b: 'My new value'
  }
}
```
npm package: @lyra/schema
Description: ## Terminology
Author: Vega
Latest version: 0.3.0

# Lyra schema

## Terminology

- **`Schema`** A collection of types
- **`Type`** A specification of a data structure. Available through schema lookup.
- **`Member type`** A member type is a type contained by a schema type. For example, an array may specify the allowed item types by defining members types from schema types. A reference may be a reference to a set of other types. A member type is not added to the schema and is not available through schema lookup, but rather exists as a property of the owner type.

## Constraints

### No inheritance

You are almost always better off using composition, rather than inheritance hierarchies

E.g.:

```js
const PERSON = {
  type: 'object',
  name: 'person',
  fields: [
    {name: 'firstName', type: 'string'},
    {
      name: 'address',
      type: 'object',
      fields: [
        {
          name: 'street',
          type: 'string'
        }
      ]
    }
  ]
}
```

If one were to introduce a user type, it would be tempting to think of it as a subtype of person, adding a few additional fields specific for the user type, like this:

```js
const USER = {
  // modelling user as a subtype of person
  name: 'user',
  type: 'person',
  fields: [
    {
      name: 'username',
      type: 'string'
    }
  ]
}
```

A problem with the above is: how do we merge the fields? Should the fields from `PERSON` be placed before the fields from `USER`? What if both types define the same field, should the subtype override? What if that field is an object where we'd like to keep some of the fields, but remove others? It quite quickly becomes messy.

A better solution would be to define common fields outside, and re-use them across types:

e.g.:

```js
const FIRST_NAME_FIELD = {name: 'firstName', type: 'string'}
const ADDRESS_FIELD = {
  name: 'address',
  type: 'object',
  fields: [
    {
      name: 'zip',
      type: 'string'
    },
    {
      name: 'street',
      type: 'string'
    },
    {
      name: 'city',
      type: 'string'
    }
  ]
}

const PERSON = {
  type: 'object',
  name: 'person',
  fields: [FIRST_NAME_FIELD, ADDRESS_FIELD]
}

const USER = {
  type: 'object',
  name: 'person',
  fields: [FIRST_NAME_FIELD, {name: 'username', type: 'string'}, ADDRESS_FIELD]
}
```

You could even take this further by extracting the individual fields of the `address` type and compose in different ways.
npm package: @lyra/uuid
Description: Simple generation of lyra document IDs
Author: Vega
Latest version: 0.3.0

# Lyra UID

Generate a valid Lyra document id

## Usage

```js
const UUID = require('./')
const id = UUID()

console.log(uid)
//=> 76dc5edf-9c43-4bab-a62d-4a2cad650053
```
npm package: @lyra/webpack-integration
Description: Tools and modules required for making partisan (the part system) work with webpack
Author: Vega
Latest version: 0.3.0

# @lyra/webpack-integration

Tools and modules required for making partisan (the part system) work with webpack. Note: currently only works with Webpack 1.

## Installing

```
npm install --save @lyra/webpack-integration
```

## Usage

```js
const lyraWebpack = require('@lyra/webpack-integration/v1')
const options = {
  basePath: '/path/to/project',
  env: 'production'
}

// Get array of plugins required for part loading
lyraWebpack.getPlugins(options)

// Get array of loader definitions required for part loading
lyraWebpack.getLoaders(options)

// Get array of postcss plugins required to build the CSS used in Lyra
lyraWebpack.getPostcssPlugins(options)

// Get a partial webpack configuration for the Lyra-specific parts. You'll have to merge this with your existing webpack config.
lyraWebpack.getConfig(options)

// Less common, but if you need more fine-grained access to internals:

// Get a preconfigured `DefinePlugin` that exposes `__DEV__`
lyraWebpack.getEnvPlugin(options)

// Get the part resolver plugin required for part imports
lyraWebpack.getPartResolverPlugin(options)

// Get the part loader (requires the PartResolverPlugin)
lyraWebpack.getPartLoader(options)

// Get the resolving function required for postcss-import
lyraWebpack.getStyleResolver(options)

// Get an initialized postcss-import plugin
lyraWebpack.getPostcssImportPlugin(options)
```

## License

MIT-licensed. See LICENSE.
npm package: @lyracom/eslint-config
Description: Lyra's ESLint config
Author: Lyra
Latest version: 5.0.2

# `@lyracom/eslint-config`

> Lyra's generic ESLint config for JavaScript / TypeScript projects.

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/eslint-config)](https://www.npmjs.com/package/@lyracom/eslint-config)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) », please follow instructions from this repo.
npm package: @lyracom/eslint-config-node
Description: Lyra's ESLint config for Node.js apps
Author: Lyra
Latest version: 4.0.2

# `@lyracom/eslint-config-node`

> Lyra's ESLint config for Node.js applications

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/eslint-config-node)](https://www.npmjs.com/package/@lyracom/eslint-config-node)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) », please follow instructions from this repo.
npm package: @lyracom/eslint-config-react
Description: Lyra's ESLint config for React apps
Author: Lyra
Latest version: 7.0.2

# `@lyracom/eslint-config-react`

> Lyra's ESLint config for React applications

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/eslint-config-react)](https://www.npmjs.com/package/@lyracom/eslint-config-react)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) », please follow instructions from this repo.
npm package: @lyracom/prettier-config
Description: Lyra's Prettier config
Author: Lyra
Latest version: 6.0.0

# `@lyracom/prettier-config`

> Lyra's Prettier config for TypeScript projects

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/prettier-config)](https://www.npmjs.com/package/@lyracom/prettier-config)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) ».
npm package: @lyracom/properties-loader
Description: Webpack loader for .properties files
Author: Lyra
Latest version: 1.0.2

# @lyracom/properties-loader

> Webpack loader for .properties files, based on the [properties](https://www.npmjs.com/package/properties) package.

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/properties-loader)](https://www.npmjs.com/package/@lyracom/properties-loader)

## Installation

```sh
yarn add -D @lyracom/properties-loader
```

or

```sh
npm install -D @lyracom/properties-loader
```

## Usage

### Webpack configuration

```js
module.exports = {
  module: {
    rules: [
      {
        test: /\.properties$/,
        loader: '@lyracom/properties-loader',
        options: {
          namespaces: true,
          sections: true,
          // other properties.parse options...
        },
      },
    ],
  },
}
```

### Webpack inline

```js
import strings from '!@lyracom/properties-loader?namespaces&sections!./strings.properties'
```

Options can be passed with a query parameter, e.g. `?namespaces&sections=false`, or a JSON object, e.g. `?{"namespaces":true,"sections":false}`.

More info here: https://webpack.js.org/concepts/loaders/#inline
npm package: @lyracom/react-native-sdk-payment-module
Description: React Native Sdk Payment Module
Author: Lyra Network
Latest version: 3.1.4

# react-native-sdk-payment-module

A React Native module for the native (iOS and Android) Lyra Payment SDK.

## Installation & usage
Documentation : https://payzen.io/fr-FR/mobp/integration_guide/react_native/

Integration App Example : https://github.com/lyra/react-native-sdk-payment-example

> [!IMPORTANT]
> @lyracom/react-native-sdk-payment-module **2.x.x** is now a TurboModule, and **requires the new architecture to be enabled and react-native 0.77+**.
>
> - If you want to use @lyracom/react-native-sdk-payment-module 2.x.x, you need to enable the new architecture in your app (see ["Enable the New Architecture for Apps"](https://github.com/reactwg/react-native-new-architecture/blob/main/docs/enable-apps.md)) and upgrade to React-Native 0.77.x
> - For React-Native 0.76.x and older, use @lyracom/react-native-sdk-payment-module 1.0.19

## Development workflow

This project is a monorepo managed using [Yarn workspaces](https://yarnpkg.com/features/workspaces). It contains the following packages:

- The library package in the root directory.
- An example app in the `example/` directory.

To get started with the project, run `yarn` in the root directory to install the required dependencies for each package:

```sh
yarn
```

The [example app](/example/) demonstrates usage of the library. You need to run it to test any changes you make.

It is configured to use the local version of the library, so any changes you make to the library's source code will be reflected in the example app. Changes to the library's JavaScript code will be reflected in the example app without a rebuild, but native code changes will require a rebuild of the example app.

If you want to use Android Studio or XCode to edit the native code, you can open the `example/android` or `example/ios` directories respectively in those editors. To edit the Objective-C or Swift files, open `example/ios/SdkPaymentModuleExample.xcworkspace` in XCode and find the source files at `Pods > Development Pods > react-native-sdk-payment-module`.

To edit the Java or Kotlin files, open `example/android` in Android studio and find the source files at `react-native-sdk-payment-module` under `Android`.

You can use various commands from the root directory to work with the project.

To start the packager:

```sh
yarn example start
```

To run the example app on Android:

```sh
yarn example android
```

To run the example app on iOS:

```sh
yarn example ios
```

To confirm that the app is running with the new architecture, you can check the Metro logs for a message like this:

```sh
Running "SdkPaymentModuleExample" with {"fabric":true,"initialProps":{"concurrentRoot":true},"rootTag":1}
```

Note the `"fabric":true` and `"concurrentRoot":true` properties.

## License

MIT

---
npm package: @lyracom/tsconfig
Description: Lyra's TypeScript configs
Author: Lyra
Latest version: 1.0.1

# `@lyracom/tsconfig`

> Lyra's TypeScript configs for JavaScript projects

## sources

[Matt Pocock TSConfig cheat sheet](https://www.totaltypescript.com/tsconfig-cheat-sheet)
[TSC Base TypeScript configs](https://github.com/tsconfig/bases)

[![npm (scoped)](https://img.shields.io/npm/v/@lyracom/tsconfig)](https://www.npmjs.com/package/@lyracom/tsconfig)

This package is part of « [Coding style for Lyra JavaScript apps](https://github.com/lyra/coding-style) ».
npm package: @lyraejs/flow
Description: A library for contains flow control thing(async)
Author: KsRyY
Latest version: 1.1.2
Deprecated: moved to @ksryy/p

# lyrae-flow

[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Flyraejs%2Flyrae-async.svg?type=small)](https://app.fossa.io/projects/git%2Bgithub.com%2Flyraejs%2Flyrae-async?ref=badge_small)  
lyrae-flow is a flow control lib, includes simple queue and chain_exec function.

## Install

``` bash
npm i @lyraejs/flow
```

To inport the module, you could use CommonJS style

``` javascript
var {queue,chainExec} = require('@lyraejs/flow');
```

or ES6 style

``` javascript
import {queue,chainExec} from '@lyraejs/flow'
```

for more API use, see the [Docs](https://lyraejs.github.io/lyrae-flow)

## Contribute

``` bash
yarn install
```

or

``` bash
npm install
```

to install the dependencies.

src/queue.js is the queue function module.

the other modules are still writing, so don't be confused with the async.js and the promise.js in the src folder

if you want to compile, just run `grunt`.

## License

[MIT](https://github.com/lyraejs/lyrae-flow/blob/master/LICENSE) @ Andy Chen
[FOSSA Report](https://app.fossa.io/attribution/8e795a62-029f-43a6-8365-64ffe665cd63)

[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Flyraejs%2Flyrae-async.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Flyraejs%2Flyrae-async?ref=badge_large)
npm package: @lyrahealth-inc/react-native-orientation-plugin
Description: Config plugin to auto configure react-native-orientation on prebuild
Author: Bryan Nguyen
Latest version: 1.0.5

# react-native-orientation-plugin

An expo config plugin created to insert native code into the compiled ios/android app and allow react-native-orientation to work with EAS build
## Setup
`npm install react-native-orientation`

`npm install @lyrahealth-inc/react-native-orientation-plugin`

Add the [config plugin](https://docs.expo.io/guides/config-plugins/) to the [`plugins`](https://docs.expo.io/versions/latest/config/app/#plugins) array of your `app.json` or `app.config.js`:

```json
{
  "expo": {
    "plugins": ["@lyrahealth-inc/react-native-orientation-plugin"]
  }
}
```

Usage:

```javscript
import Orientation from 'react-native-orientation';

Orientation.lockToPortrait();
```

Reference [react-native-orientation](https://github.com/yamill/react-native-orientation) library for more documentation.