open-index/open-npm huggingface dataset:
npm package: @lomray/prettier-config
Description: This package provides Lomray .prettier as an extensible shared config.
Author: Mikhail Yarmaliuk
Latest version: 2.1.0

# prettier-config

This package provides Lomray base JS (Typescript) .prettierrc.js as an extensible shared config.

## Usage

1. Install package:

```sh
npm i --save-dev @lomray/prettier-config
```

2. Example you .prettierrc.js.
```js
import config from '@lomray/prettier-config';

export default {
	...config,
};
```
npm package: @lomray/react-mobx-manager
Description: This package provides Mobx stores manager for react.
Author: Mikhail Yarmaliuk
Latest version: 4.3.0

# React MobX Manager

<p align="center">
    <img  src="./logo.png" alt="Mobx stores manager logo" width="250" height="253">
</p>

Clean React components. Encapsulated business logic. No state-tree pain.

It is built for apps that want explicit store ownership, SSR support, persistence, lifecycle cleanup and development tooling without forcing everything into one global state tree.

## Why use it

- One way to escape state tree 🌲🌳🌴.
- Ready to use with Suspense.
- Support SSR.
- Support render to stream.
- Relative stores for component-owned state
- Parent stores for subtree reuse
- Global stores for app-wide state
- Small package size.
- Support code splitting out of the box.
- Access stores from other stores.
- Can be a replacement for react context.
- Persistence support
- Vite plugin support
- Best-effort HMR
- And many other nice things 😎

<p align="center">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=reliability_rating" alt="reliability">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=security_rating" alt="Security Rating">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=sqale_rating" alt="Maintainability Rating">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=vulnerabilities" alt="Vulnerabilities">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=bugs" alt="Bugs">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=ncloc" alt="Lines of Code">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=Lomray-Software_react-mobx-manager&metric=coverage" alt="code coverage">
  <img src="https://img.shields.io/bundlephobia/minzip/@lomray/react-mobx-manager" alt="size">
  <img src="https://img.shields.io/npm/l/@lomray/react-mobx-manager" alt="size">
  <img src="https://img.shields.io/npm/v/@lomray/react-mobx-manager?label=semantic%20release&logo=semantic-release" alt="semantic version">
</p>

## Install

```bash
npm i @lomray/react-mobx-manager @lomray/consistent-suspense
```

## Documentation

Full documentation lives in [here](https://lomray-software.github.io/react-mobx-manager/)

## License
Made with 💚

Published under [MIT License](./LICENSE).
npm package: @lomray/react-native-navigation-manager
Description: React native navigation manager for wix react-native-navigation.
Author: Mikhail Yarmaliuk
Latest version: 1.4.1

<h1 align='center'>React native navigation manager</h1>

### Manager for [react-native-navigation](https://github.com/wix/react-native-navigation)

### Key features:

- More flexible control your navigation.
- Navigation tree under hand.
- Get state in any time.

## Table of contents
- [Getting started](#getting-started)
- [How to use](#how-to-use)
- [License](#license)

## Getting started

The package is distributed using [npm](https://www.npmjs.com/), the node package manager.

```
npm i --save @lomray/react-native-navigation-manager
```

## How to use

1. Create instance of navigation manager:
```typescript
import { NavigationManager } from '@lomray/react-native-navigation-manager'

const manager = new NavigationManager();

export default manager;
```
2. Use navigation manager instead original navigation:

```typescript jsx
import NavigationManager from './navigation-manager';

// Run as soon as possible
NavigationManager.listen();

// Use manager instead base navigation
NavigationManager.push({
  component: {
    name: 'my-scfreen',
  },
});

// Get latest component id in tree
console.log(NavigationManager.current.getComponentId());
console.log(NavigationManager.current.getStackId());
console.log(NavigationManager.current.getModalId());
console.log(NavigationManager.current.getOverlayId());
```

## Bugs and feature requests

Bug or a feature request, [please open a new issue](https://github.com/Lomray-Software/react-native-navigation-manager/issues/new).

## License
Made with 💚

Published under [MIT License](./LICENSE).
npm package: @lomray/reactotron-mobx-store-manager
Description: This package provides reactotron plugin for mobx stores manager.
Author: Mikhail Yarmaliuk
Latest version: 1.2.0

# Reactotron plugin for [Mobx stores manager](https://github.com/Lomray-Software/react-mobx-manager)

[![Reliability Rating](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=reliability_rating)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)
[![Security Rating](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=security_rating)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)
[![Maintainability Rating](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=sqale_rating)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)
[![Vulnerabilities](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=vulnerabilities)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)
[![Bugs](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=bugs)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)
[![Lines of Code](https://sonarcloud.io/api/project_badges/measure?project=reactotron-mobx-store-manager&metric=ncloc)](https://sonarcloud.io/summary/new_code?id=reactotron-mobx-store-manager)

<p float="center">
  <img src="https://raw.githubusercontent.com/Lomray-Software/reactotron-mobx-store-manager/staging/example/demo1.jpg" alt="Reactotron demo 1" width="300"/>
  <img src="https://raw.githubusercontent.com/Lomray-Software/reactotron-mobx-store-manager/staging/example/demo2.jpg" alt="Reactotron demo 2" width="300"/>
</p>

## Table of contents

- [Getting started](#getting-started)
- [Bugs and feature requests](#bugs-and-feature-requests)
- [Copyright](#copyright)


## Getting started

The package is distributed using [npm](https://www.npmjs.com/), the node package manager.

```
npm i --save-dev @lomray/reactotron-mobx-store-manager
```

In your `ReactotronConfig.js`:

```jsx
import MobxStoreManagerPlugin from '@lomray/reactotron-mobx-store-manager';

const reactotron = Reactotron
  .configure()
  .use(MobxStoreManagerPlugin()) // connect plugin
  .connect()
```

## Bugs and feature requests

Bug or a feature request, [please open a new issue](https://github.com/Lomray-Software/reactotron-mobx-store-manager/issues/new).

## Copyright

Code and documentation copyright 2022 the [Lomray Software](https://lomray.com/).
npm package: @lomray/rollup-plugin-generate-package-json-v2
Description: Generate package.json file with packages from your bundle using Rollup
Author: Vlad Shcherbin
Latest version: 1.0.0

# rollup-plugin-generate-package-json

[![Build Status](https://travis-ci.org/vladshcherbin/rollup-plugin-generate-package-json.svg?branch=master)](https://travis-ci.org/vladshcherbin/rollup-plugin-generate-package-json)
[![Codecov](https://codecov.io/gh/vladshcherbin/rollup-plugin-generate-package-json/branch/master/graph/badge.svg)](https://codecov.io/gh/vladshcherbin/rollup-plugin-generate-package-json)

Generate `package.json` file with packages from your bundle using Rollup.

V2 Fork allow exclude packages from dependencies section.

## About

This plugin is useful when you have a lot of packages in your current `package.json` file and want to create a lean one with only packages from your generated bundle, probably for deployment.

## Installation

```bash
# yarn
yarn add rollup-plugin-generate-package-json -D

# npm
npm install rollup-plugin-generate-package-json -D
```

## Usage

```js
// rollup.config.js
import generatePackageJson from 'rollup-plugin-generate-package-json'

export default {
  input: 'src/index.js',
  output: {
    file: 'dist/app.js',
    format: 'cjs'
  },
  plugins: [
    generatePackageJson()
  ]
}
```

### Configuration

There are some useful options, all of them are optional:

#### excludeDependencies

Type: `array`\
Default: `[]`

Exclude packages from dependencies section.

```js
generatePackageJson({
    excludeDependencies: ['package-name']
})
```

#### inputFolder

Type: `string`\
Default: `current working directory`

Set input `package.json` folder.

```js
generatePackageJson({
  inputFolder: 'nested/folder'
})
```

#### outputFolder

Type: `string`\
Default: `bundle output folder`

Set output folder for generated `package.json` file.

```js
generatePackageJson({
  outputFolder: 'dist'
})
```

#### baseContents

Type: `object | function`\
Default: `{}`

Set base contents for your generated `package.json` file.

```js
generatePackageJson({
  baseContents: {
    scripts: {
      start: 'node app.js'
    },
    dependencies: {},
    private: true
  }
})
```

It can also be a function, which receives the contents of the input `package.json` file.

```js
generatePackageJson({
  baseContents: (pkg) => ({
    name: pkg.name,
    main: pkg.main.replace('src', 'dist'),
    dependencies: {},
    private: true
  })
})
```

#### additionalDependencies

Type: `Array | object`\
Default: `[]`

Set dependencies which are not directly imported in the bundle, but are used by the app.

```js
generatePackageJson({
  additionalDependencies: ['pg']
})
```

It's also possible to add new dependencies or overwrite dependency version.

```js
generatePackageJson({
  additionalDependencies: {
    pg: '7.12.1',
    'react-calendar': 'file:../react-calendar/react-calendar-v2.13.2.tgz'
  }
})
```

## License

MIT
npm package: @lomray/rollup-plugin-img
Description: import image files with rollup
Author: alwaysolinetxm
Latest version: 1.2.3

# rollup-plugin-img

Import image files with rollup. Let you import images just like what you do with webpack in your React code!

THIS FORK ADD NEXT OPTIONS: addRequire, addExtraRequire, pathHandler, outputPathHandler, extraExtensions


## Installation

    yarn add --dev rollup-plugin-img
    
or 

    npm install -D rollup-plugin-img
    
## Usage

In the rollup.config.js:

```JavaScript
import image from 'rollup-plugin-img';

export default {
  entry: 'src/index.js',
  dest: 'dist/bundle.js',
  plugins: [
    image({
      limit: 10000
    })
  ]
};
```

and in your React code:

```JavaScript
import img from 'path/image.png';

  ...
  render() {
    return <img src={ img } />;
  }
  ...
```

## Options

You can pass an option to the `image()` just like above, and there are some options:

- exclude & include: Optional. like other rollup plugins. [Details](https://github.com/rollup/rollup/wiki/Plugins)
- output: Required. the dest path of output image files. The first directory of dest will be handled as the base output directory(where the html file will be, usually).
- extensions: Optional. a regular expression for the extensions of image files.
- limit: Optional. the limit(byte) of the file size. A file will be transformed into base64 string when it doesn't exceeded the limit, otherwise, it will be copyed to the dest path.
- hash: Optional. a boolean value to indicate wheather to generate a hash string in file name(default false).

demo:

```JavaScript
  ...
  image({
    output: `${distPath}/images`, // default the root
    extensions: /\.(png|jpg|jpeg|gif|svg)$/, // support png|jpg|jpeg|gif|svg, and it's alse the default value
    limit: 8192,  // default 8192(8k)
    exclude: 'node_modules/**'
  })
  ...
```

## License

MIT
npm package: @lomray/strapi-firebase-auth
Description: Firebase auth plugin.
Author: Lomray Software
Latest version: 1.0.6

# Strapi plugin for firebase authentication

## Getting started

The package is distributed using [npm](https://www.npmjs.com/), the node package manager.

```
npm i --save @lomray/strapi-firebase-auth
```

## How it works:
1. Get firebase token in your app (e.g.: `auth().currentUser.getIdToken()`)
2. Call API POST `/api/firebase/login` with `{"token": "your-firebase-token"}`
3. Use returned jwt token to call Strapi API (if the user does not exist it will be created automatically).

If Strapi JWT token expired, just call `/api/firebase/login` again.

**NOTE**: Configure plugin before use, see `Firebase Credentials` in Settings section (Admin Panel).  
**NOTE2**: Add `phone` and `photoUrl` fields to user entity for save related firebase fields (not required).

## Report Bugs/Issues
Any bugs/issues you may face can be submitted as issues in the GitHub repo.
npm package: @lomray/stylelint-config
Description: This package provides Lomray stylelint config as an extensible shared config.
Author: Mikhail Yarmaliuk
Latest version: 2.0.1

# stylelint-config

This package provides Lomray base stylelint config as an extensible shared config.

## Usage

1. Install package:

```sh
  npm i --save-dev @lomray/stylelint-config
```

2. Add `extends: ["@lomray/stylelint-config"]` to your .stylelintrc.js
npm package: @lomray/vite-ssr-boost
Description: Vite plugin for create awesome SSR or SPA applications on React.
Author: Mikhail Yarmaliuk
Latest version: 7.1.0

# Vite SSR BOOST

<p align="center">
    <img src="https://raw.githubusercontent.com/Lomray-Software/vite-ssr-boost/prod/logo.png" alt="Vite SSR BOOST logo" width="250" height="250">
</p>

SSR and SPA toolkit for React Router apps on top of Vite.

It is built for applications that want to keep Vite and React Router visible, but still need the practical runtime layer for SSR, SPA fallback, streaming, custom entrypoints and deployment-oriented builds.

## Why use it

- SSR and SPA from one route tree
- React Router on both client and server
- stream rendering with request lifecycle hooks
- a Vite-native plugin and CLI flow
- Switch between SPA and SSR in 1 second.
- response-aware helpers such as redirects and status codes
- custom entrypoints for mobile, embedded and service-worker-friendly shells

<p align="center">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=reliability_rating" alt="reliability">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=security_rating" alt="Security Rating">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=sqale_rating" alt="Maintainability Rating">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=vulnerabilities" alt="Vulnerabilities">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=bugs" alt="Bugs">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=ncloc" alt="Lines of Code">
  <img src="https://sonarcloud.io/api/project_badges/measure?project=vite-ssr-boost&metric=coverage" alt="code coverage">
  <img src="https://img.shields.io/npm/v/@lomray/vite-ssr-boost?label=semantic%20release&logo=semantic-release" alt="semantic version">
</p>

## Install

```bash
npm i @lomray/vite-ssr-boost
```

## Documentation

Full documentation lives here: [lomray-software.github.io/vite-ssr-boost](https://lomray-software.github.io/vite-ssr-boost/)

## License

Made with 💚

Published under [MIT License](./LICENSE).
npm package: @lomux/lomux
Description: Universal local AI gateway — route any coding agent through GitHub Copilot
Latest version: 0.3.0

# lomux

Use your GitHub Copilot subscription with Cline, Codex, and Claude Code.

## Installation

```bash
npm install -g lomux
```

## Supported Platforms

| Platform | Architecture | npm Package          |
| -------- | ------------ | -------------------- |
| macOS    | arm64        | `@lomux/darwin-arm64` |
| macOS    | x64          | `@lomux/darwin-x64`   |
| Linux    | x64          | `@lomux/linux-x64`    |
| Linux    | arm64        | `@lomux/linux-arm64`  |
| Windows  | x64          | `@lomux/win32-x64`    |

## How it works

When you run `lomux`, the shim:

1. Detects your platform and resolves the matching `@lomux/<os>-<arch>` optional
   dependency
2. Runs the native binary directly — no Deno runtime required
3. If no platform binary is available, falls back to
   `deno run jsr:@lomux/lomux` (requires [Deno](https://deno.land) installed)
4. If neither is available, prints an error with a link to manual download

## Manual Download

Download pre-built binaries from the
[GitHub Releases](https://github.com/lomux/lomux/releases) page.
npm package: @lona/compiler
Description: Lona cross-platform code compiler
Author: Mathieu Dutour
Latest version: 0.2.1

# Lona Compiler

![Build and Test](https://github.com/Lona/compiler/workflows/Build%20and%20Test/badge.svg)

The Lona Compiler is a CLI tool for generating cross-platform UI code from JSON definitions.

The Lona Compiler is published on `npm` as `@lona/compiler`.

## Usage

### Installation

First, install the compiler with:

```bash
npm install --global @lona/compiler
```

You may also install locally to your current project if you prefer, by removing the `--global`.

### Commands

For each command, you'll choose a code generation `format`: `swift`, `js`, `tokens`, or `documentation`.

Each format as a specific set of options.

In the case of `js`, the `--framework` option can have a few values:

- `reactnative`: [React Native](https://facebook.github.io/react-native/) (default)
- `reactdom`: [React DOM](https://reactjs.org)
- `reactsketchapp`: [React SketchApp](http://airbnb.io/react-sketchapp/)

#### Generate workspace

This will generate the colors, text styles, shadows, custom types, and all components, writing them to `output-directory` in the same structure as the input workspace directory.

```bash
lona convert [path-to-workspace-directory] --format=js --output=[output-directory]
```

## Contributing

To build the compiler from source, follow these steps.

This project is written in TypeScript.

### Setup: Install dependencies with yarn

From this directory, run:

```bash
yarn
```

> Note: If you don't have yarn installed already, you can download it with npm: `npm install --global yarn`

### Running commands

The above examples can now be run by replacing `lona` with `ts-node src/bin.ts`.
npm package: @lona/migrate-legacy-tokens
Description: Lona originally used a flat list of colors/shadows/textStyles to represent tokens.
Latest version: 1.0.1

# Migrate legacy tokens

Lona originally used a flat list of colors/shadows/textStyles to represent tokens.

To convert a file in this format to the new (markdown + code) format, navigate to the root of your Lona workspace (or wherever the JSON files are), and run:

```
npx @lona/migrate-legacy-tokens colors.json > Colors.md
npx @lona/migrate-legacy-tokens textStyles.json > TextStyles.md
npx @lona/migrate-legacy-tokens shadows.json > Shadows.md
```
npm package: @lona/serialization
Description: Convert Lona files between serialization formats
Author: Devin Abbott
Latest version: 0.7.0

# Lona Serialization

![Build and Test](https://github.com/Lona/serialization/workflows/Build%20and%20Test/badge.svg)

Convert Lona files between JSON, and source code (Swift + MDX).

## Overview

Lona token files are typically stored as [MDX](https://mdxjs.com/) (Markdown with embedded React components).

Token files support a special kind of code block, marked with the language "tokens", that contains Lona token definitions. These definitions can be stored as JSON, or (a small subset of) Swift. This utility converts between the different formats.

### API

#### `convertDocument: (String, Format) -> String`

Supported formats: `'json'`, `'source'`

Example: Convert a `.md` document to JSON

```js
import { convertDocument } from '@lona/serialization'

const lonaDocument = '...' // source code of a Lona document

const lonaJson = convertDocument(lonaDocument, 'json')
```

#### `convertLogic: (String, Format) -> String`

Supported formats: `'json'`, `'source'`

Example: Convert a `.tokens` file to JSON

```js
import { convertLogic } from '@lona/serialization'

const lonaTokens = '...' // source code of a Lona tokens file

const lonaJson = serialization.convertLogic(lonaTokens, 'json')
```
npm package: @lona/site-components
Description: Components for Lona-generated websites
Latest version: 0.0.5

# Site Components

Lona uses these components on generated websites.

Some day, they'll be replacable by the developer for custom theming.

## API

See the [example](/example) for usage.

In order to support websites powered by Next, Gatsby, etc, you'll likely want to provide a custom `Link` component via the `LinkContext`. For example:

```js
import { LinkContext, LinkProps } from '@lona/site-components'

// This is the default Link component
const Link = (props: LinkProps) => <a {...props} />

function App() {
  return (
    <LinkContext.Provider value={Link}>
      {/* Your components here */}
    </LinkContext.Provider>
  )
}
```

You can optionally modify the `href` prop if needed, or use it to determine which component to render (e.g. for internal vs external urls).
npm package: @lona/svg-model
Description: ![](./docs/logo.png)
Latest version: 3.0.0-alpha.11

![](./docs/logo.png)

# SVG Model

A simplified model to represent SVGs for drawing on a 2D canvas. This is useful when building an SVG renderer.

## How it works

All SVG elements are converted to a flat list of paths. Group attributes (e.g. styles, transforms) are already applied to each path. Paths are simplified to the minimal set of commands needed for accurate drawing.
npm package: @lona/workspace-to-sketch-library
Description: Generate a Sketch library from a Lona workspace
Author: Mathieu Dutour
Latest version: 0.3.1

# workspace-to-sketch-library

Generate a Sketch library from a Lona Workspace.

## Installation

```bash
npm install @lona/workspace-to-sketch-library lonac
```

## Usage

```js
import generateLibrary from '@lona/workspace-to-sketch-library'

generateLibrary(workspacePath, outputPath, options)
```

All options are optional.

- `options.compiler`: path to the Lona compiler to use (will default to the installed `lonac` compiler's path)
- `options.devicePresetList`: array of device presets (`{ name, width, height }`)
- `options.componentPathFilter`: function that returns a boolean depending on whether a component should be included in the library or not. It receives the path to the component as argument
- `options.logFunction`: a function to log the progress (typically, `console.log`)