open-index/open-npm huggingface dataset:
npm package: @sarina/core
Description: Sarina is a minimal and flexible NodeJs framework that lets you write modern, fast and easy use applications.
Author: Mohammad Parvareshi Hamrah
Latest version: 1.0.1

[![Build Status](https://travis-ci.org/SarinaJs/Sarina.svg?branch=master)](https://travis-ci.org/SarinaJs/Sarina)


# Sarina
Sarina is a minimal and flexible NodeJs framework that lets you write moder, fast, easy application.

# Sarina/Core
This repository is core package of Sarina including Dependency Injection, Error handling, Appliaction bootstrap

## Quickstart

[Get started in 5 minutes][quickstart].

## Changelog

[Learn about the latest improvements][changelog].
npm package: @sarissa/pagination
Description: Add page number buttons for pagination. Automaticly add and disable numbers as current page number.
Author: iozcelik
Latest version: 1.0.3

# @sarissa/pagination

Add page number buttons for pagination. Automaticly add and disable numbers as current page number.

<img width="505" alt="image" src="https://user-images.githubusercontent.com/10682780/162905825-223f3257-c2a9-494d-bc56-ddcb075ec2f4.png">

## Installation
```js
npm install @sarissa/pagination
```

## Usage
```js
import { Pagination } from "@sarissa/pagination";

//Must set your total page count
const totalPage = 10;
---
<style is:global>
      .activeButton {
        --tw-bg-opacity: 1;
        background-color: rgb(239 68 68 / var(--tw-bg-opacity));
        color: wheat;
      }
</style>

<Pagination currentPage="1" {totalPage} url="posts" />

<Pagination currentPage="3" {totalPage} url="posts" activeButton="activeButton"
    />
```

### Component Props

Name | Description
--- | --- 
outerDiv | Outer div style of pagination buttons (default: flex items-center justify-center)
buttonGroup | Style of button group (no default)
button | Style of all page number buttons (default: relative flex-nowrap inline-flex items-center px-4 py-2 border text-sm font-medium)
activeButton | Style of active page button (default: bg-sky-500 text-white)
disabledButton | Style of disabled buttons (default: disabled:opacity-75)
currentPage | Current page number (required)
totalPage | Total page numbers (required)
url | Url of slug (required. ex: 'post','categories')
npm package: @saritasa/confusing-browser-globals
Description: A list of browser globals that are often used by mistake instead of local variables
Latest version: 1.0.2

# confusing-browser-globals

**This package will be frozen then Facebook ends work on CRAv2, cause it's originally a part of CRAv2** 

A curated list of browser globals that commonly cause confusion and are not recommended to use without an explicit `window.` qualifier.

## Motivation

Some global variables in browser are likely to be used by people without the intent of using them as globals, such as `status`, `name`, `event`, etc.

For example:

```js
handleClick() { // missing `event` argument
  this.setState({
  	text: event.target.value // uses the `event` global: oops!
  });
}
```

This package exports a list of globals that are often used by mistake. You can feed this list to a static analysis tool like ESLint to prevent their usage without an explicit `window.` qualifier.


## Installation

```
npm install --save confusing-browser-globals
```


## Usage

If you use Create React App, you don't need to configure anything, as this rule is already included in the default `eslint-config-react-app` preset.

If you maintain your own ESLint configuration, you can do this:

```js
var restrictedGlobals = require('confusing-browser-globals');

module.exports = {
  rules: {
    'no-restricted-globals': ['error'].concat(restrictedGlobals),
  }
};
```


## License

MIT
npm package: @saritasa/cordova-build-utils
Description: Cordova specific utils to prepare build of an application.
Author: Danil Sidorkin
Latest version: 1.0.2

# Cordova build tools

This package contains Cordova specific build utilities.

## Tips:
Use `hooks/setVersionAndBundleId` as "before_build" cordova hook, because on "before_prepare" build config options are not presented in a Cordova context instance on this step.

# Features:
1. [Versioning](#Versioning) - uses unified approach to set version code  and version name for both: Android and iOS.
1. [Build number information](#Build-number-information) - adds build number info like `1.0.0.build-100` to show builds from CI in Firebase App Distribution as different builds e.g.
1. [Set bundle ID](Set-bundle-ID) - use `bundleId` from extended Cordova build config as `id` attribute of widget in config.xml. Both sections (debug and release) can contain different bundle ID.

## Versioning

The `setVersionAndBundleId` hook retrieve version from the main `package.json` (used as source of truth) using the `utils/version.js` and create two kind of versions:
1. Version name (`version` attribute in `config.xml`) - SemVer from the `package.json` as is. Uses as "displayable" value.
1. Version code (`android-versionCode` and `ios-CFBundleVersion`) - number presentation of version. Uses approach of Android platform (see [docs](https://cordova.apache.org/docs/en/latest/guide/platforms/android/index.html#setting-the-version-code) for more details). We reuse the same approach for both platforms to get unified approach for version code to prevent confusing and easily detect that Android and iOS applications are the same version or not.

## Build number information

The `utils/version.js` also retrieve build number from the `BUILD_NUMBER` environment variable and if it presented, the `setVersionAndBundleId` hook add this information to the version name or skip this step if the `BUILD_NUMBER` is not presented or is empty/not a number. 

The `BUILD_NUMBER` automatically provided by Jenkins e.g. and you don't have to do it manually but if you want skip this step (usually for prod buildings) you can just set it to an empty string before call build command.

```
BUILD_NUMBER='' <build command>
```

## Set bundle ID

This utilities package support dynamically changing bundleId of an application during building process.
The `setVersionAndBundleId` retrieves `bundleId` property from certain section (platform + mode) of used `build.json` file. If the `bundleId` is not presented then this step will be skipped and original `bundleId` in `config.xml` will no be changed.

For instance if you want to use different bundle ID for release build you should add `bundleId` into the release section for certain platforms:

``` json
{
	"ios": {
		"debug": {
			// Not bundleId presented then bundleID from config.xml will be used
		},
		"release": {
			...,
      "bundleId": "com.bundleid.for.release.mode"
		}
	},
	"android": {
    "debug": {
			// Not bundleId presented then bundleID from config.xml will be used
		},
		"release": {
			...,
      "bundleId": "com.bundleid.for.release.mode"
		}
	}
}

```
npm package: @saritasa/create-react-app
Description: Create React apps with no build configuration.
Latest version: 1.5.4

# create-react-app

This package includes the global command for [Create React App](https://github.com/facebook/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebook/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.
npm package: @saritasa/eslint-config-base
Description: Saritasa's shareable base config for eslint
Author: Konstantin Petryaev
Latest version: 1.0.0

# @saritasa/eslint-config-base

Config is based on airbnb's config with prettier, eslint-comments and import plugins
1. Install `@saritasa/eslint-config-base` and peer dependencies (npm warns about them) 

    ```sh
    $ npm install --save-dev @saritasa/eslint-config-base
    ```

2. Add `"extends": "@saritasa/eslint-config-base"` to your `.eslintrc` file
npm package: @saritasa/eslint-config-core
Description: Saritasa core configuration of ESLint
Author: Saritasa
Latest version: 1.0.3

# Core ESLint configuration

This package contains the core ESLint configuration that we're using in the Saritasa
across all of our JavaScript/TypeScript projects.

This package works strictly with ESLint version equal or greater than 9.x.

If you need to configure ESLint that is version 8.x please use the deprecated `@saritasa/eslint-config-saritasa` package.
The specific version of this deprecated package that works with ESLint 8.0 is 2.1.7.
npm package: @saritasa/eslint-config-saritasa
Description: ESLint configuration for typescript.
Author: Saritasa
Latest version: 3.0.0

# ESLint configuration for typescript

## Installation

1.  ```bash
    npm i -D @saritasa/eslint-config-saritasa
    ```
2. ```js
    // eslint.config.js
    import config from '@saritasa/eslint-config-saritasa';
    ```
3.  Add config to the `"extends"` property in `eslint.config.js`
4.  Add linting script in your `package.json`
5.  Run `npm run lint`

## Dependencies

Latest version available for each version of ESLint

| @saritasa/eslint-config-saritasa | ESLint      |
| -------------------------------- | ----------- |
| 2.1.7                            | < 9.x       |
| 3.x                              | >= 9 .x     |