open-index/open-npm huggingface dataset:
npm package: @jict/prettier-config
Description: Shared prettier configuration.
Author: justInCaseTechnologies Inc.
Latest version: 0.0.4

# `@jict/prettier-config`

[![npm version](https://badge.fury.io/js/%40jict%2Fprettier-config.svg)](https://badge.fury.io/js/%40jict%2Fprettier-config.svg)

Shared prettier configuration.

## Installation

```bash
$ yarn add --dev @jict/prettier-config
```

## Usage

Shared prettier config comes bundled in `@jict/prettier-config`. To enable these rules, add a `prettier` property in your `package.json` and reference this shared config as follows:

```
"prettier": "@jict/prettier-config"
```

Previously, rules had been defined directly in a `.prettierrc` or `package.json` 

Any previous `.prettierrc` should be removed in favour of the shared config.
npm package: @jict/stylelint-plugin
Description: justInCaseTechnologies&#x27;s stylelint rules and config.
Author: justInCaseTechnologies Inc.
Latest version: 2.0.9

# `@jict/stylelint-plugin`

[![npm version](https://badge.fury.io/js/%40jict%2Fstylelint-plugin.svg)](https://badge.fury.io/js/%40jict%2Fstylelint-plugin.svg)

justInCaseTechnologies's stylelint rules and config.

## Installation

Install [stylelint](https://stylelint.io/) and `@jict/stylelint-plugin`:

**With Yarn**
```
yarn add --dev stylelint @jict/stylelint-plugin
```

**With npm**
```
npm install stylelint @jict/stylelint-plugin --save-dev
```

## Usage

justInCaseTechnologies's stylelint rules come bundled in `@jict/stylelint-plugin`. To enable these rules, add a `stylelint` property in your `package.json`. See the [stylelint configuration docs](https://stylelint.io/user-guide/configuration/) for more details.
```
"stylelint": {
  "extends": ["@jict/stylelint-plugin"]
}
```

Now you can run stylelint by adding the following linting script to your `package.json`. See the [stylelint CLI docs](https://stylelint.io/user-guide/cli/) for more details.
```
"scripts": {
  "stylelint": "stylelint 'src/**/*.scss'"
}
```
Run it:

**With Yarn**
```
yarn run stylelint
```

**With npm**
```
npm run stylelint
```

## Prettier

This config also includes a prettier config which can be extended to format `.scss`.
Using the [`stylelint-prettier`](https://github.com/bpscott/stylelint-prettier) plugin, prettier changes are exposed as stylelint rule violations.

Install [`prettier`](https://github.com/prettier/prettier):

```
$ yarn add --dev prettier
```

Extend the config in your `package.json`:

```json
"stylelint": {
  "extends": [
    "@jict/stylelint-plugin/prettier"
  ]
}
```

Add a prettier config in `package.json`:

```json
"prettier": {
  "singleQuote": true,
  "trailingComma": "es5",
  "bracketSpacing": false
}
```

Prettier fixes shall be reported when you run `stylelint **/*.css` and shall be autofixed when you run `stylelint --fix **/*.scss`.
npm package: @jict/typescript-configs
Description: A set of typescript configuration files that can be extended.
Author: justInCaseTechnologies Inc.
Latest version: 1.0.0

# `@jict/typescript-configs`

[![npm version](https://badge.fury.io/js/%40jict%2Ftypescript-configs.svg)](https://badge.fury.io/js/%40jict%2Ftypescript-configs.svg)

In TypeScript, the configuration file can extend from a base file. This package provided a few common base configuration files to simplify TypeScript project setup.

To read more about how this extensibility works. See [typescript handbook](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html#configuration-inheritance-with-extends).

Below are two documentation we have also found useful to have on hand while setting up a configuration file.

- [`tsconfig.json`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html)
- [Compiler Options](https://www.typescriptlang.org/docs/handbook/compiler-options.html)

## Installation

```bash
$ yarn add --dev @jict/typescript-configs
```

## Usage

### React Application Project

To start, create a `tsconfig.json` in the root of your project.

A typical setup where the application sit in `[project root]/app` folder is as follow:

```json
{
  "extends": "@jict/typescript-configs/application.json",
  "compilerOptions": {
    "baseUrl": ".",
    "rootDir": ".",
    "paths": {"*": ["*", "app/*"]}
  },
  "include": ["app", "client", "server", "tests"]
}
```


### Next.js Application Project

A base configuration for your Next.js project.

```json
{
  "extends": "@jict/typescript-configs/nextjs.json",
  "include": ["src", "next-env.d.ts"]
}
```

### React Library Project

Similarly for a react library project. Create a `tsconfig.json` in the root of your project with a setup below assuming the library code sit in `[project root]/src` folder.

```json
{
  "extends": "@jict/typescript-configs/library.json",
  "compilerOptions": {
    "baseUrl": "./src",
    "rootDir": "."
  },
  "include": ["./src/**/*"]
}
```

### Project that run in the browser

A configuration file is provided that included styles setup and a more conservative build target.

```json
{
  "extends": "@jict/typescript-configs/dom.json",
  "compilerOptions": {
    "baseUrl": ".",
    "rootDir": "."
  }
}
```

### All Other Project

A base configuration file is also provided if the above does not fit your need.

```json
{
  "extends": "@jict/typescript-configs/base.json",
  "compilerOptions": {
    "baseUrl": ".",
    "rootDir": "."
  }
}
```

### Common Got Ya

#### Type Checking does not honour `skipLibCheck: true` setting

There are times when the type failure occur inside of a library your project is consuming, and having `skipLibCheck: true` does not resolved it. In this scenario, add an `exclude` option to your `tsconfig.json`.

eg.

```json
{
  "extends": "@jict/typescript-configs/base.json",
  "compilerOptions": {
    "baseUrl": ".",
    "rootDir": ".",
    "exclude": ["./node_modules/**/*"]
  }
}
```
npm package: @jidebiao/components
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Latest version: 0.18.11

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

- Configure the top-level `parserOptions` property like this:

```js
export default {
  // other rules...
  parserOptions: {
    ecmaVersion: 'latest',
    sourceType: 'module',
    project: ['./tsconfig.json', './tsconfig.node.json'],
    tsconfigRootDir: __dirname,
  },
}
```

- Replace `plugin:@typescript-eslint/recommended` to `plugin:@typescript-eslint/recommended-type-checked` or `plugin:@typescript-eslint/strict-type-checked`
- Optionally add `plugin:@typescript-eslint/stylistic-type-checked`
- Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and add `plugin:react/recommended` & `plugin:react/jsx-runtime` to the `extends` list