open-index/open-npm huggingface dataset:
npm package: @peterek/eslint-config-base
Description: ESLint configuration base to use prettier & standard configurations
Author: Jiri Peterek
Latest version: 1.0.2

# @peterek/eslint-config-base

An ESLint [shareable config](http://eslint.org/docs/developer-guide/shareable-configs)
base for language specific configurations using **Prettier** and **JavaScript Standard Style** as ESLint
rules.

> This is a base configuration for more language specific configs such as `@peterek/eslint-config-js` or `@peterek/eslint-config-ts`. DO NOT USE DIRECTLY!

## Usage

### ESLint config

This package has two main files (`base` & `end`). To ensure all the extending configurations align with prettier & standard configs, you have to put all other extends between these modules.

```json
{
  "extends": [
    "@peterek/base/start",

    // all the additional configurations should be put here,

    "@peterek/base/end"
  ]
}
```
npm package: @peterek/eslint-config-js
Description: ESLint configuration for JavaScript projects
Author: Jiri Peterek
Latest version: 1.0.1

# @peterek/eslint-config-js

An ESLint [shareable config](http://eslint.org/docs/developer-guide/shareable-configs)
for projects using **Prettier** and **JavaScript Standard Style** as ESLint
rules.

## Installation

These instructions assume that you've already installed ESLint
(`npm i -D eslint`) and **@babel/eslint-parser** (`npm i -D @babel/eslint-parser`).

```sh
# install @peterek/eslint-config-js
npm i -D @peterek/eslint-config-js

# install exact version of prettier to achieve consistent results over time
npm i -ED prettier
```


## Usage

### ESLint config

Once you've finished installation, add @peterek/eslint-config-js to the
"extends" array in your [ESLint configuration](https://eslint.org/docs/user-guide/configuring/configuration-files). Make sure to put it last, so that
it gets the chance to override other configs that could conflict with Prettier.

```json
{
  "extends": [
    "@peterek/js"
  ]
}
```

<details>
<summary>ESLint config recommendations</summary>

It is up to your judgement to specify environment used within project and also to specify whether it's a root repository so the ESLint does not look for another configs up in the file path.

```json
{
  "root": true,
  "env": {
    "browser": true,
    "es2021": true
  },
  "extends": [
    "@peterek/js"
  ]
}
```
</details>

### Prettier config

Make sure you have created prettier config file (`.prettierrc`) with following content:

```json
"prettier-config-standard"
```

### Update package.json scripts

Update `scripts` section in `package.json` file to include following **lint** entry:

```json
{
  "scripts": {
    "lint": "eslint --fix --ext .cjs,.mjs,.js,.ts,.jsx,.tsx --format codeframe ."
  }
}
```
npm package: @peterek/vite-plugin-favicons
Description: Simple Vite plugin to generate favicons from source image. Nothing more, nothing less.
Author: Jiri Peterek
Latest version: 2.1.0

# @peterek/vite-plugin-favicons
Simple Vite plugin using [favicons](https://github.com/itgalaxy/favicons) library under the hood
to generate favicons with manifest files from yor source image. Nothing more, nothing less.

1. Add plugin to your Vite configuration
    ```js
    // vite.config.js
    import favicons from '@peterek/vite-plugin-favicons'

    export default {
      plugins: [
        favicons('src/assets/icon.svg')
      ]
    }
    ```

1. Then just enter `<!-- FAVICONS -->` comment at the end of head section in the `index.html` file
```html
<!DOCTYPE html>
<html lang="en">
  <head>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>My Vite app</title>
    <!-- FAVICONS -->
  </head>
  <body>
    <div id="app"></div>
    <script type="module" src="/src/main.ts"></script>
  </body>
</html>

```


## Contribution

You're free to contribute to this project by submitting [issues](https://github.com/josh-hemphill/vite-plugin-favicon/issues) and/or [pull requests](https://github.com/josh-hemphill/vite-plugin-favicon/pulls).

## License

This project is licensed under [MIT](https://github.com/josh-hemphill/vite-plugin-favicon/blob/latest/LICENSE).

[favicons]: https://github.com/haydenbleasel/favicons
npm package: @peterek/vite-plugin-font
Description: Vite plugin for simple use of custom fonts
Author: Jiri Peterek
Latest version: 3.0.1

# @peterek/vite-plugin-font
Vite plugin for simple use of custom fonts

## Use in [Vite config](https://vitejs.dev/config/) file

### Minimal configuration

```js
import { join } from 'node:path'

import { font } from '@peterek/vite-plugin-font'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    font({
      font: {
        name: 'Roboto',
        src: join(__dirname, 'assets/Roboto/*.ttf'),
      },
    })
  ]
})
```

### Full configuration

```js
import { join } from 'node:path'

import { font } from '@peterek/vite-plugin-font'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    font({
      // Base directory for the font files to be accessed from (optional).
      // Default: `UserConfig['base'] + 'fonts'`
      base: '/',

      // Font definitons. It can be defined as single object or as list of configurations
      font: [
        {
          // Font name to be referenced by css rule e.g.: `font-family: Roboto;`
          name: 'Roboto',
          // Absolute path to the font sources using glob pattern
          src: join(__dirname, 'assets/Roboto/*.ttf'),
          // The `font-display` descriptor used for each font-face (optional). Default: 'auto'
          display: 'auto',
        },
      ],

      // Location where inject link tags to (optional). Default: 'head-prepend'
      injectLinkTo: 'head-prepend',

      // Location where inject link tags to (optional). Default: 'head'
      injectStyleTo: 'head',

      // Prefetch fonts. If true, takes precedence over preload option (optional). Default: `false`
      prefetch: false,

      // Preload fonts (optional). Default: `false`
      preload: true,
    })
  ]
})
```