open-index/open-npm huggingface dataset:
npm package: @lokalise/comments-ui
Description: A sidebar component that displays Lokalise projects', keys', and translations' comments and provides callbacks to perform comments CRUD operations as well comments list interactions.
Author: Lokalise
Latest version: 1.1.1

# Comments Sidebar

A sidebar component that displays Lokalise projects', keys', and translations' comments and provides callbacks to perform comments CRUD operations as well comments list interactions.

## How to develop locally

We will be using [yalc](https://github.com/wclr/yalc) to symlink the Comments Sidebar package locally in your application. The following steps assuming you're using it in `lokalise-main` app. but you can follow the same procedures with any other app. like `review-center`

1. Run `npm run dev`  
   The package will be built and published to store when you see the following message:-

```
@lokalise/comments-sidebar@X.X.X published in store.
```

2. In your app (in this example lokalise-ui), add the package using yalc

```
cd lokalise-main/services/app/lokalise-ui
npx yalc add @lokalise/comments-sidebar
```

The script will copy the current version to `.yalc` folder and update your `package.json` with `file:.yalc/@lokalise/comments-sidebar`

3. To install `@lokalise/comments-sidebar` peer depedncies

```
npm i
```

4. In your app, start importing `CommentsSidebar` component, your IDE shall pick it up from `@lokalise/comments-sidebar`

5. Any changes in `lokalise-comments-sidebar` project, will be built and copied automatically to your dependent project.

6. Don't forget to discard any changes in your dependent project after finishing your changes testing
npm package: @lokalise/content-conversion-schemas
Description: > **Deprecated** — this package is a re-export barrel kept for backward compatibility only. > New consumers should depend directly on the focused packages instead: > > - **`@lokalise/content-conversion-api-schemas`** — domain/API schemas (frontend-safe
Latest version: 11.2.0

# Content-conversion events schemas

> **Deprecated** — this package is a re-export barrel kept for backward compatibility only.
> New consumers should depend directly on the focused packages instead:
>
> - **`@lokalise/content-conversion-api-schemas`** — domain/API schemas (frontend-safe, no messaging dependencies)
> - **`@lokalise/content-conversion-event-schemas`** — SNS/SQS event contracts (backend-only)

This library contains schemas and types related to content-conversion events.
npm package: @lokalise/eslint-config-frontend
Description: Shareable eslint config for frontend codebases
Author: Rupert Foggo McKay
Latest version: 4.6.1

# eslint-config-frontend

Shareable ESLint config for frontend codebases

## Using this config

Install the config in your repo:

```shell
npm add -D eslint @lokalise/eslint-config-frontend
```

Then add the following to `.eslintrc.json` in the root of your project:

```json
{
  "extends": "@lokalise/eslint-config-frontend"
}
```

Finally, add a package script in your `package.json` as follows:

```json
{
  "scripts": {
    "lint": "eslint . --ext .js,.ts,.jsx,.tsx,.cjs"
  }
}
```

Feel free to customize the `--ext` CLI arg according to your project needs.

Note that this shareable config needs to know where your `tsconfig` is located in order to be able to parse TypeScript code. By default it will _assume_ that your `tsconfig` is in the same directory as your eslint config. If that's the case, it'll work without any additional configuration. However if that is not the case, you will need to explicitly tell it where the `tsconfig` in your repo is. For example:

```json
{
  "extends": "@lokalise/eslint-config-frontend",
  "parserOptions": {
    "project": "../tsconfig.json"
  }
}
```

## Modular Configuration

The default config assumes that you have a stack including:

- TypeScript
- React
- Vitest

However you can pick and choose just the parts you like.

The following modular configs are available:

- `@lokalise/eslint-config-frontend/core`
- `@lokalise/eslint-config-frontend/typescript`
- `@lokalise/eslint-config-frontend/react`
- `@lokalise/eslint-config-frontend/vitest`
- `@lokalise/eslint-config-frontend/localisation`
- `@lokalise/eslint-config-frontend/testingLibrary`

We recommend you always pick `core`, but suppose the only other one you need is `typescript`, then you would add the following to your eslint config:

```json
{
  "extends": [
    "@lokalise/eslint-config-frontend/core",
    "@lokalise/eslint-config-frontend/typescript"
  ]
}
```

## Support Us

lokalise-npm-package-template was created by Lokalise Engineering Team. Support our work by keeping this line in your README.
npm package: @lokalise/eslint-config-lokalise-frontend
Description: Shareable eslint config for frontend codebases
Author: Rupert Foggo McKay
Latest version: 1.0.3

# eslint-config-lokalise-frontend

Shareable eslint config for frontend codebases

## Using this config

Install the config in your repo:

```shell
npm add -D eslint @lokalise/eslint-config-lokalise-frontend
```

Then add the following to `.eslintrc.json` in the root of your project:

```json
{
  "extends": "@lokalise/eslint-config-lokalise-frontend"
}
```

Finally add a package script in your `package.json` as follows:

```json
"scripts": { 
  "lint": "eslint . --ext .js,.ts,.jsx,.tsx,.cjs",
},
```

Feel free to customize the `--ext` CLI arg according to your project needs.

Note that this shareable config needs to know where your `tsconfig` is located in order to be able to parse TypeScript code. By default it will _assume_ that your `tsconfig` is in the same directory as your eslint config. If that's the case, it'll work without any additional configuration. However if that is not the case, you will need to explicitly tell it where the `tsconfig` in your repo is. For example:

```json
{
  "extends": "@lokalise/eslint-config-lokalise-frontend",
  "parserOptions": {
    "project": "../tsconfig.json"
  }
}
```

## Modular Configuration

The default config assumes that you have a stack including:

- TypeScript
- React
- Jest

However you can pick and choose just the parts you like.

The following modular configs are available:

- `@lokalise/eslint-config-lokalise-frontend/core`
- `@lokalise/eslint-config-lokalise-frontend/typescript`
- `@lokalise/eslint-config-lokalise-frontend/react`
- `@lokalise/eslint-config-lokalise-frontend/jest`

We recommend you always pick `core`, but suppose the only other one you need is `typescript`, then you would add the following to your eslint config:

```json
{
  "extends": [
    "@lokalise/eslint-config-lokalise-frontend/core",
    "@lokalise/eslint-config-lokalise-frontend/typescript"
  ]
}
```