open-index/open-npm huggingface dataset:
npm package: @plesk/eslint-config
Description: Plesk ESLint config
Author: Alexey Sinko
Latest version: 4.0.1

# Plesk ESLint Config

ESLint configuration for Plesk projects

[![NPM version](https://img.shields.io/npm/v/@plesk/eslint-config.svg)](https://www.npmjs.org/package/@plesk/eslint-config)
[![NPM Downloads](https://img.shields.io/npm/dm/@plesk/eslint-config.svg)](https://www.npmjs.org/package/@plesk/eslint-config)


## Installation

```
npm install --save-dev eslint @plesk/eslint-config
```


## Usage

Example of `eslint.config.mjs`:
```js
import plesk from "@plesk/eslint-config";

export default [
    plesk,
    {
      // your overrides here
    }
] 
```
npm package: @plesk/eslint-plugin-plesk
Description: Plesk ESLint plugin
Author: Evgenii Karagodin
Latest version: 0.2.0

# Plesk ESLint Plugin

Custom ESLint rules for Plesk projects

[![NPM version](https://img.shields.io/npm/v/@plesk/eslint-plugin-plesk.svg)](https://www.npmjs.org/package/@plesk/eslint-plugin-plesk)
[![NPM Downloads](https://img.shields.io/npm/dm/@plesk/eslint-plugin-plesk.svg)](https://www.npmjs.org/package/@plesk/eslint-plugin-plesk)


## Installation

```
npm install --save-dev @plesk/eslint-plugin-plesk
```


## Usage

Put into your `.eslintrc`
```json
{
  "plugins": "@plesk/eslint-plugin-plesk"
}
```
npm package: @plesk/plesk-ext-sdk
Description: Plesk Extension SDK
Author: Plesk Developers
Latest version: 0.8.0

# Plesk Extension SDK

[![npm version](https://badge.fury.io/js/%40plesk%2Fplesk-ext-sdk.svg)](https://www.npmjs.com/package/@plesk/plesk-ext-sdk)
[![Build Status](https://travis-ci.com/plesk/plesk-ext-sdk.svg?branch=master)](https://travis-ci.com/plesk/plesk-ext-sdk)

It's a toolkit for development extensions for Plesk.

## Documentation

- [Getting Started](/docs/01-getting-started.md#getting-started)
- [Extension SDK Features](/docs/02-extension-sdk-features.md#extension-sdk-features)
- [Code Quality Tools](/docs/03-code-quality-tools.md#code-quality-tools)

## License

Apache 2.0
npm package: @plesk/stylelint-config
Description: Stylelint shareable config for Plesk projects
Author: Plesk
Latest version: 3.0.1

# Plesk Stylelint Config

Stylelint configuration for Plesk projects

[![NPM version](https://img.shields.io/npm/v/@plesk/stylelint-config.svg)](https://www.npmjs.org/package/@plesk/stylelint-config)
[![NPM Downloads](https://img.shields.io/npm/dm/@plesk/stylelint-config.svg)](https://www.npmjs.org/package/@plesk/stylelint-config)

## Installation
Install a compatible version of stylelint.
```
# with npm:
npm install --save-dev stylelint @plesk/stylelint-config

# with yarn:
yarn add --dev stylelint @plesk/stylelint-config
```

## Usage

Put into your `.stylelintrc`
```json
{
  "extends": "@plesk/stylelint-config",
  "rules": {
    // Add overrides and additional rules here
  }
}
```
npm package: @plesk/ui-library
Description: Plesk UI Library
Author: Plesk Developers
Latest version: 3.46.5

# UI Library

## Installation

```
yarn add @plesk/ui-library
```

## Usage

Here is an example of how to use the UI Library with `create-react-app`.

```shell
yarn create react-app example
cd example
yarn add @plesk/ui-library
yarn start
```

Replace the contents of the `src/App.js` file with the following code:

```js
import { Layout, Button } from '@plesk/ui-library';
import '@plesk/ui-library/dist/plesk-ui-library.css';

function App() {
    return (
        <Layout>
            <Button>{'Hello World!'}</Button>
        </Layout>
    );
}

export default App;
```

## Development

Sometimes you need to fix UI Library bug that fires in your project using UI Library.

There is a way to test dev version of the UI Library with your project. You need to use `yarn link` command,
but there are some details.

* First, you need to run `yarn link` in your UI Library working copy root directory.
* Then, you need to run `yarn link @plesk/ui-library` in your project working copy root directory.
* Third. There is a bug with a React library that makes us to do additional steps. Run `yarn link` in your
project's `node_modules/react` and `node_modules/react-dom` directories.
* Then, run `yarn link react` and `yarn link react-dom` in your UI Library working copy root directory.

So, in this setup, your project will use the dev copy of UI Library. And UI Library will use React from your project.

## Deployment

UI Library in Plesk is updated automatically per commit basis. UI Library master build is published to the [internal artifactory](https://artifacts.plesk.tech/ui/repos/tree/General/npm-ui-library/@plesk/ui-library/-/@plesk),
bumped in Plesk and pull request is sent to Plesk code owners.

For other projects, please refer to the [official documentation](https://webpros.atlassian.net/wiki/spaces/UX/pages/3653307347/How+To+Publish+New+Version).