open-index/open-npm huggingface dataset:
npm package: @sonarinno/jodit-react
Description: Jodit is awesome and usefully wysiwyg editor with filebrowser
Author: Chupurnov
Latest version: 1.0.65

# React Jodit WYSIWYG Editor

[![npm](https://img.shields.io/npm/v/jodit-react.svg)](https://www.npmjs.com/package/jodit-react)
[![npm](https://img.shields.io/npm/dm/jodit-react.svg)](https://www.npmjs.com/package/jodit-react)
[![npm](https://img.shields.io/npm/l/jodit-react.svg)](https://www.npmjs.com/package/jodit-react)

React wrapper for [Jodit](https://xdsoft.net/jodit/)

## Installation

```bash
npm install jodit-react --save
```

## Update editor version
```bash
npm update jodit-react
```

## Run demo
```bash
npm install --dev 
npm run demo
```

and open
```
http://localhost:4000/
```

## Usage

### 1. Require and use Jodit-react component inside your application.

```jsx
import React, {useState, useRef} from 'react';
import JoditEditor from "jodit-react";

const Example = ({}) => {
	const editor = useRef(null)
	const [content, setContent] = useState('')
	
	const config = {
		readonly: false // all options from https://xdsoft.net/jodit/doc/
	}
	
	return (
            <JoditEditor
            	ref={editor}
                value={content}
                config={config}
		tabIndex={1} // tabIndex of textarea
		onBlur={newContent => setContent(newContent)} // preferred to use only this option to update the content for performance reasons
                onChange={newContent => {}}
            />
        );
}
```


License
-----
This package is available under `MIT` License.
npm package: @sonarly/sourcemap-uploader
Description: NPM module to upload your JS sourcemaps files to Sonarly
Author: Alex Tsokurov
Latest version: 3.0.13

# sourcemap-uploader

An NPM module to upload your JS sourcemap files to your Sonarly instance.

## Installation

```
npm i -D @Sonarly/sourcemap-uploader
```

## CLI

### Upload a sourcemap for one file:

```bash
sourcemap-uploader -s https://sonarly.mycompany.com/api -k API_KEY -p PROJECT_KEY file -m ./dist/index.js.map -u https://myapp.com/index.js
```

For local development:
```bash
sourcemap-uploader -s http://localhost:8081/api -k API_KEY -p PROJECT_KEY file -m ./dist/index.js.map -u http://localhost:8081/assets/index.js
```

### Upload all sourcemaps in a given directory. 
The URL must correspond to the root where you upload JS files from the directory. In other words, if you have your `app-42.js` along with  the `app-42.js.map` in the `./build` folder and then want to upload it to your Sonarly instance so it can be reachable through the link `https://myapp.com/static/app-42.js`, then the command should be like:

```bash
sourcemap-uploader -s https://sonarly.mycompany.com/api -k API_KEY -p PROJECT_KEY dir -m ./build -u https://myapp.com/static
```

- Use `-s` (`--server`) to specify the URL of your Sonarly instance (must include /api path).
**Do not use this parameter if you use SaaS version of Sonarly (defaults to https://api.sonarly.dev)**

- Use `-l` (`--logs`) to enable verbose logging and see detailed request/response information.

## NPM

There are two functions you can export from the package:

```
uploadFile(api_key, project_key, sourcemap_file_path, js_file_url, [server])
uploadDir(api_key, project_key, sourcemap_dir_path, js_dir_url, [server])
```

Both functions return Promise with a result value to be the list of files for which sourcemaps were uploaded.

## Dev

```
npm install
bash run-dev.sh
```
npm package: @sonarsoftware/karma-basic-text-reporter
Description: A basic reporter that generates test results to a text file. 
Author: Matthew Rynbrand
Latest version: 1.0.4

# karma-basic-text-reporter

Generates a file based on all current failing tests.

### Installation
```sh
$ npm i @sonarsoftware/karma-basic-text-reporter --save-dev
```

### Usage
In your karma config file add `@sonarsoftware/karma-basic-text-reporter` to your plugins.
```sh
plugins: ['karma-*', '@sonarsoftware/karma-basic-text-reporter'],
```

Next add it to your reporters.
```sh
reporters: ['mocha', '@sonarsoftware/basicTextReporter']
```

Then add the config option, passing in your desired file location, and file extension (currently only supports json).

```sh
'@sonarsoftware/basicTextReporter': {
    path: path.resolve(__dirname, './../../reports/'),
    extension: '.json'
}
```

### TODO
 - More formats, e.g. Html, YML, etc.
 - Tests 
 - Automatic cloud storage uploading (Google Drive, Dropbox)
npm package: @sonarsource/gatsby-theme-marketing
Description: Gatsby theme for Sonar projects
Author: Lucio Merotta
Latest version: 5.2.1

# **Sonar Gatsby theme**

## **Purpose**

- Standardize the list of dependencies needed for Martech maintained websites
- Provide a starting set of common gatsby plugins preinstalled, and minimum options to configure them
- Provide easy integration with Kentico Kontent.
- Use the [Sonar Design System](https://www.npmjs.com/package/sonar-design-system)

## **How to use it**

This theme is included in the boilerplate by default. If you want to use it somewhere else, simply install the `gatsby-theme-sonar` dependency, and enable it in your gatsby config.

## **Options**

- `projectId (string)`: the Kentico Kontent project id
- `previewKey (string)`: The Kentico Kontent preview key
- `secureKey (string)`: The Kentico Kontent secure access key
- `previewMode (boolean)`: if true, the project will use the preview API from Kentico Kontent
- `managementKey (string)`: The Kentico Kontent management key
- `typesToGenerate (string[] | undefined)`: see the [GraphQL transformer plugin](../gatsby-transformer-kontent-graphql/README.md) docs
- `homepageCodename (string | undefined)`: The codename of the homepage in Kentico Kontent. If not specified, defaults to `homepage`
- `disablePageGeneration (boolean | undefined)`: If true, will disable the default page generation algorithm. Useful if you are integrating the theme in an existing website that has its own page generation algorithm.
- `layout (string | undefined)`: The root layout of your pages, as specified by `gatsby-plugin-layout`. if not specified, will use the `MainLayout` from the theme.

## **Included plugins**

- `@sonarsource/marketing-gatsby-transformer-kontent-graphql`
- `gatsby-plugin-emotion`
- `gatsby-plugin-image`
- `gatsby-plugin-layout`
- `gatsby-plugin-sharp`
- `gatsby-plugin-tsconfig-paths`
- `gatsby-transformer-sharp`
npm package: @sonarsource/marketing-design-system
Description: Design system for Sonar marketing projects
Author: Sonar Source SA
Latest version: 5.2.1

# Sonar Design System

**[View Storybook](https://sonar-design-system.netlify.app/)**

## Usage

### Installation

```sh
yarn add sonar-design-system
```

### Implementation

```js
// App.tsx
import { ThemeProvider, Button } from 'sonar-design-system';

const App = () => (
  <ThemeProvider>
    <Button variant="primary">Primary Button</Button>
  </ThemeProvider>
);
```

### Releases

```sh
# Test all components
yarn test
# Create a new build
yarn build
# Choose new version and publish build to repository
yarn publish
```

## Storybook

### Start

```sh
yarn storybook
```

### Build

```
yarn build-storybook
```

### Deploy

Commit to `master`

## Theming

### Available themes:

- `mercury` _default_
- `gemini`

### Available shades:

- `light` _default_
- `dark`

### Overwrite default theme

```js
// App.tsx
import { ThemeProvider, Button } from 'sonar-design-system';

const App = () => (
  <ThemeProvider theme="gemini" shade="dark">
    <Button />
  </ThemeProvider>
);
```

### Get or modify current theme and shade

```js
// Button.tsx
import { useTheme } from 'sonar-design-system';

const Button = () => {
  const { theme, shade, setTheme, setShade } = useTheme();
  return <button />;
};
```

## Fonts

### Import directly

```js
import 'sonar-design-system/dist/fonts/maven-pro.woff2';
import 'sonar-design-system/dist/fonts/saira.woff2';
```

### Import by CSS

```js
import 'sonar-design-system/dist/css/fonts.css';
```