open-index/open-npm huggingface dataset:
npm package: @ksquareincmx/zanma-ui
Description: ## Install
Author: Michell Ayala
Latest version: 0.4.1

# @ksquareincmx/zanma-ui

## Install

```bash
npm install --save @ksquareincmx/zanma-ui
```

## Usage

> Note:
> For the UI library to work properly first you must
> add "Raleway" font family to your application

```tsx
import * as React from "react";

import { Text } from "@ksquareincmx/zanma-ui";

class Example extends React.Component {
  render() {
    return <Text>Hell world</Text>;
  }
}
```

## License

MIT © [KsquareIncMx](https://github.com/ksquareincmx)
npm package: @ksryy/p
Description: A library that contains some promise api
Author: KsRyY
Latest version: 2.1.7
Deprecated: No longer maintained

[![Build Status](https://travis-ci.com/kry-org/p.svg?branch=master)](https://travis-ci.com/kry-org/p) [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fkry-org%2Fp.svg?type=small)](https://app.fossa.io/projects/git%2Bgithub.com%2Fkry-org%2Fp?ref=badge_small) [![Known Vulnerabilities](https://snyk.io/test/github/KsRyY/q/badge.svg?targetFile=package.json)](https://snyk.io/test/github/KsRyY/q?targetFile=package.json) [![Greenkeeper badge](https://badges.greenkeeper.io/kry-org/p.svg)](https://greenkeeper.io/)

<a href="http://github.com/kry-org/p">
    <img src="https://raw.githubusercontent.com/kry-org/p/master/p.png" align="right" alt="P Logo" />
</a>  

A small promise library, inspired by [q](https://github.com/kriskowal/q)

***Notice:this library shouldn't be used in browser enviroment unless any further notice. [more](https://kry-org.github.io/p/#/browserwarn)***

## Browser Avaliable Feature List

- [x] fcall
- [x] pcall

## Install

``` bash
npm i @ksryy/p
```

To inport the module, you could use CommonJS style

``` javascript
var {fcall,pcall} = require('@ksryy/p');
```

or ES6 style

``` javascript
import {fcall,pcall} from '@ksryy/p'
```

for more API use, see the [Docs](https://kry-org.github.io/p)

## Contribute

``` bash
yarn install
```

or

``` bash
npm install
```

to install the dependencies.

/src/p.js is the sourcecode.
/p.js is the compiled code (by @babel).

if you want to compile, just run `grunt`.
if you want to run test suite, use `jest`

## License

[MIT](https://github.com/kry-org/p/blob/master/LICENSE) @ Andy Chen
[FOSSA Report](https://app.fossa.io/attribution/ab8170a5-24d8-49ae-8ede-ed51cd4ff3f7)

[![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fkry-org%2Fp.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Fkry-org%2Fp?ref=badge_large)
npm package: @ksryy/parallel-async
Description: A zero-dependency async parallel task runner
Author: Andy Chen
Latest version: 2.0.2

# parallel-async

***Moved to `@ksryy/parallel-async` due to OTP misconfiguration (may move back in a few days)***

> A zero-dependency async parallel task runner. Powered by Promise.

*NOTE: This package is designed for both Webpack and Node.js usage, but if you are using a enviroment that does not support Promise (such as IE) you need to polyfill it by yourself.*

## Install

``` bash
npm install @ksryy/parallel-async
```

Then import it use either CommonJS:
``` js
const parallel = require('parallel-async');
```
or ESModule:
``` js
import parallel from 'parallel-async'
```

## Usage (more of a mixture of guideline and design idea)

First you need to pass two parameters to the `parallel` function. One object and one callback function.

The object contains two things: the task list (property `tasks`) and a optional parameter that will be passed to the ***outer layer function***.

The `tasks` property should be an `Array`. It contains the task that you want to run.

You can see that I emphasized the "outer layer function". This library is powered by `Promise`, so the task should orginally recieve only two parameter, `resolve` and `reject` as in [Using promises at MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises), but what if you want to give your task something from outside that only works in the task function's scope? The solution is to wrap your function that will return a function that actually become the `Promise`. The ***outer layer*** will recieve that thing as a parameter, and then the ***outer layer*** will retern the ***inner layer*** function that actually executes in the promise. Because of  closure, the ***inner function*** can still access the variables in the ***outer function's scope***. Here's a example:
``` js
functon eg(param) {
  return function (resolve,reject) {}
}
```
The returned function is what actually run in the `Promise`.

**The only way to pass in the task list is to use an `Array` now, because I no longer use `for...of` loops for better polyfillability**

There is also something tricky about the callback function that you need to provide. The callback function **won't** be called more than once now, but if an error occured, all results of previously runned tasks will be discarded, no matter they successed or not.