# after-async-data

> 在获得某结果前进行排队，等获取结果后再运行。

Latest version **1.0.1** (published 2020-07-02) · ISC license · 0 weekly downloads

## Install

```sh
npm install after-async-data
pnpm add after-async-data
yarn add after-async-data
bun add after-async-data
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.1 |
| Published | 2020-07-02 |
| First published | 2020-07-01 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 11.6 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 1 |
| Author | forever-z-133 |
| Maintainers | forever-z |
| Keywords | wait-queue, wait-before-task, data-cache |

## Links

- npm: https://www.npmjs.com/package/after-async-data
- Repository: https://github.com/forever-z-133/after-async-data
- Issues: https://github.com/forever-z-133/after-async-data/issues
- npm.io page: https://npm.io/package/after-async-data

## Alternatives

- [memory-cache](https://npm.io/package/memory-cache.md) — 795.0K weekly downloads
- [@httptoolkit/proxy-agent](https://npm.io/package/@httptoolkit/proxy-agent.md) — 11.2K weekly downloads
- [express-cache-controller](https://npm.io/package/express-cache-controller.md) — 5.3K weekly downloads
- [http-cache-middleware](https://npm.io/package/http-cache-middleware.md) — 4.5K weekly downloads
- [cache2](https://npm.io/package/cache2.md) — 1.5K weekly downloads

## Recent versions

- 1.0.1 (latest) — 2020-07-02
- 1.0.0 — 2020-07-01

## README

# after-async-data

在获得某结果前进行排队，等获取结果后再运行。

## 安装

```
npm i -S after-async-data
```

## 如何使用

```js
import AfterAsyncData from "~after-async-data";
const waitQueue = new AfterAsyncData.getInstance();
waitQueue.add(type, (params, next) => {}, params);
waitQueue.get(type, (result, isCache) => {});
waitQueue.remove(type, onlyRemoveCache);
```

> #### 比如在进入应用后直接调用了多个接口，但后来需在之前加上 getToken 方法

```js
import AfterAsyncData from "~after-async-data";
const waitQueue = new AfterAsyncData.getInstance();

// 伪·业务代码
const getToken = (uid, next) => setTimeout(() => next("token"), 500);
var ajax = (params, success, fail) => setTimeout(() => success(params), 500);
const getUserInfo = (callback) => ajax(null, callback);
const getIndexData = (callback) => ajax(null, callback);

// 先注册前置函数
waitQueue.add("get token before ajax", getToken, 'uid');
// 包装原方法，把原逻辑置于获取结果之后
const _ajax = ajax;
var ajax = (params, success, fail) => {
  waitQueue.get("get token before ajax", (token, isCache) => {
    !isCache && localStorage.setItem("token", token);
    _ajax(params, success, fail);
  });
}

// 再调用业务代码时，会等到获取 token 后才运行
getUserInfo(() => console.log('userInfo'));
getIndexData(() => console.log('indexData'));
```

> #### 用于缓存一点异步数据

```js
var getLargeData = (next) => setTimeout(() => next({}), 500);
waitQueue.add("cache large data", getLargeData);
const _getLargeData = getLargeData;
var getLargeData = (callback) => {
  waitQueue.get("cache large data", (largeData) => {
    _getLargeData(callback);
  });
}
// 业务代码运行后，data 会存入插件缓存，下次再调用会先取缓存
// 使用 waitQueue.remove('cache large data', false) 可清掉缓存
getLargeData();
```

> #### 结合上述两者，可处理很多等待数据的场景

比如在 app.js 获取权限，在 index.js 获取完数据后就要用，  
但这两个异步谁先谁后其实并不确定，又因为跨页面而无法 Promise.all,  
则可通过本 `after-async-data` 插件来进行等待。

再比如，在某个节点前只接收操作但不反馈，等满足条件后再筛选操作再运行。

当然，本案例实现得可能并不甚妙，欢迎 issuse 和 pull request 交流。

---
_Source: https://npm.io/package/after-async-data · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._