@flare-engine/achievements

中文文档
0.4.12发布于 2026/11/13Apache-2.0TypeScriptESM + CJS零依赖构建来源已验证近 30 天下载 2302

Achievements provider interface (consumer-supplied adapter)

原始使用文档
文档目录4 节
  1. Install
  2. Usage
  3. Local providers + the unlock contract
  4. Env-gated fallback

@flare-engine/achievements

Typed AchievementsProvider interface + NoopAchievementsProvider + React context, plus createMemoryAchievements / createStorageAchievements — local providers with a defined unlock/progress contract, for tests, dev, and single-player games. Concrete platform adapters (Game Center, Google Play Games, Steam) are post-launch; wire your own at the app boundary until then.

Install

bun add @flare-engine/achievements

Usage

import {
  AchievementsContext,
  useAchievements,
  NoopAchievementsProvider,
} from '@flare-engine/achievements';

export function App() {
  return (
    <AchievementsContext.Provider value={NoopAchievementsProvider}>
      {/* ... */}
    </AchievementsContext.Provider>
  );
}

useAchievements() returns the active provider. The AchievementsProvider surface is unlock(id, progress?), getState(id), and getAll() — all async. Progress is a partial [0, 1] value; omit it to fully unlock.

Local providers + the unlock contract

createMemoryAchievements() keeps state in memory; createStorageAchievements(store, opts?) persists it through an injected { get, set } store. Both share the same contract — the semantics adapter authors should preserve:

import { createStorageAchievements } from '@flare-engine/achievements';
import type { AchievementsStore } from '@flare-engine/achievements';

declare const myStore: AchievementsStore;

const achievements = createStorageAchievements(myStore); // { get, set }

await achievements.unlock('first_blood', 0.5); // progress 0.5
await achievements.unlock('first_blood', 0.2); // ignored — progress stays 0.5
await achievements.unlock('first_blood');      // full unlock, latches
await achievements.getState('first_blood');    // { unlocked: true, progress: 1, unlockedAt }
  • Clamped + monotonic: progress is clamped to [0, 1] (non-finite → 0) and never decreases — a lower requested value is ignored.
  • unlock(id) fully unlocks (target progress 1).
  • Latches: reaching progress 1 sets unlocked: true and stamps unlockedAt once (via the injected now, default Date.now). Re-unlocking is a no-op — the original unlockedAt is kept.
  • Untracked ids report { unlocked: false, progress: 0 }.

AchievementsStore is a structural { get(key): Promise<string | null>; set(key, value): Promise<void> } — the get/set subset of @flare-engine/storage's StorageAdapter, so the storage provider adds no dependency and works with any async KV (AsyncStorage, an MMKV wrapper, a localStorage shim, …). It hydrates lazily from store.get(key) (default key 'flare.achievements'), persists after every mutation, and serializes writes so concurrent unlocks can't lose an update.

Env-gated fallback

In CI or dev builds without platform credentials, select NoopAchievementsProvider (or a local provider) behind your own env flag so nothing touches a native SDK until real credentials are present.

版本与发布记录

@flare-engine/achievements 共发布 17 个版本,首次发布于 2026/06/10;过去 12 个月发布了 17 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.4.12latest2026/11/133 天前
0.4.112026/11/123 天前
0.4.102026/11/087 天前
0.4.82026/11/0610 天前
0.4.72026/11/0411 天前
0.4.62026/10/3115 天前

关于 @flare-engine/achievements 的常见问题

@flare-engine/achievements 是什么?

Achievements provider interface (consumer-supplied adapter)

如何安装 @flare-engine/achievements?

在项目目录运行 npm install @flare-engine/achievements,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:react(>=19.0.0)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@flare-engine/achievements 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@flare-engine/achievements 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@flare-engine/achievements 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=20。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@flare-engine/achievements 可以商用吗?

@flare-engine/achievements 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@flare-engine/achievements 的下载量有多少?

根据 npm 官方下载统计,@flare-engine/achievements 在 2026/10/15 – 2026/11/13 这 30 天内被下载 2,302 次,日均约 77 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@flare-engine/achievements 还在维护吗?

最新版本 0.4.12 发布于 2026/11/13(3 天前);至今共发布 17 个版本,其中过去 12 个月发布了 17 个;首次发布于 2026/06/10。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。