npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

spa-api-provider

v2.0.1

Published

React Context API Provider for handling game data

Downloads

336

Readme

API Provider (spa-api-provider)

A React context provider for embedded CAPTRS SPAs (survey-builder, mini-games, etc.): configuration, game data, scores, events, and typed helpers that call the game-platform HTTP APIs (via axios).

Installation

npm install spa-api-provider

Use ^2.0.1 (or >=2.0.1) so the AI chat discriminator serializes as lineage (Jackson / Kotlin defaults). 2.0.0 used modelLineage, which does not bind server-side — see 2.0.1 in CHANGELOG.md. Team comms: RELEASE.md.

Usage

Import and wrap your app

import React from 'react';
import { ApiProvider } from 'spa-api-provider';

const App = () => {
  return (
    // Optional: <ApiProvider apiUrl="https://api.example.com" token="your-token">
    <ApiProvider>
      <YourComponent />
    </ApiProvider>
  );
};

export default App;

Using the API context

import { useApi } from 'spa-api-provider';

const YourComponent = () => {
  const { getGameScores, saveGameScore, platformContext } = useApi();

  const fetchScores = async () => {
    const scores = await getGameScores();
    console.log(scores);
  };

  console.log(platformContext?.exerciseId);
  console.log(platformContext?.organizationId);

  return (
    <div>
      <button onClick={fetchScores}>Get Scores</button>
    </div>
  );
};

AI chat (POST /api/ai/chat)

From useApi(), aiChat(params) posts JSON matching the platform AIChatRequestDTO: include lineage (PLATFORM_MANAGED or CLIENT_OVERRIDE) — the JSON name matches the Kotlin property under Jackson defaults. Type exports: AiModelLineage, AIChatRequestDTO (discriminated union), optional assertAIChatRequestRuntime for dynamic input.

Platform-managed — omit models (do not send an empty array):

import { useApi, AiModelLineage } from 'spa-api-provider';

const { aiChat } = useApi();

await aiChat({
  lineage: AiModelLineage.PLATFORM_MANAGED,
  messages: [{ role: 'user', content: 'Hello' }],
});

Client overridemodels is required (non-empty at runtime):

import { useApi, AiModelLineage } from 'spa-api-provider';

const { aiChat } = useApi();

await aiChat({
  lineage: AiModelLineage.CLIENT_OVERRIDE,
  models: ['gpt-4.1-mini'],
  messages: [{ role: 'user', content: 'Hello' }],
});

See CHANGELOG.md (v2.0.1) for the lineage wire key. If you are on 2.0.0, replace modelLineage with lineage.

Platform context (optional)

useApi() exposes an optional platformContext object:

  • exerciseId?: string
  • appInstanceId?: string
  • gameConfigId?: string (explicit value if provided, otherwise derived from appInstanceId)
  • organizationId?: string
  • rawConfig?: Record<string, unknown>

All fields are optional. Apps that only use providerConfig (apiUrl and token) keep working as before.

The provider normalizes these from incoming CONFIG messages in this order:

  1. camelCase top-level fields
  2. snake_case top-level fields
  3. context.* fallbacks