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

@algolia/experiences

v0.1.1

Published

Algolia Experiences loader script

Readme

@algolia/experiences

Evergreen loader script for Algolia Experiences.

Bundles

| Bundle | Use case | | ------------------------ | ----------------------------------------------- | | experiences.js | Production sites | | experiences.preview.js | Staging sites, Algolia Dashboard (live editing) |

Usage

Production

Add the loader script to your HTML with your Algolia credentials and experience ID as URL parameters:

<script src="https://cdn.jsdelivr.net/npm/@algolia/experiences/dist/experiences.js?appId=YOUR_APP_ID&apiKey=YOUR_API_KEY&experienceId=YOUR_EXPERIENCE_ID"></script>

Preview

Use the preview bundle on staging environments for live editing:

<script src="https://cdn.jsdelivr.net/npm/@algolia/experiences/dist/experiences.preview.js?appId=YOUR_APP_ID&apiKey=YOUR_API_KEY&experienceId=YOUR_EXPERIENCE_ID"></script>

The preview bundle reads algolia_experiences_config from the page URL. This allows to add the parameter to the iframe URL, or users to share preview links:

https://example.org/page?algolia_experiences_config=BASE64_CONFIG

The loader decodes the base64 JSON and passes it to AlgoliaExperiences.run(config).

const config = { title: 'Café ☕', theme: 'dark' };
const encoded = btoa(encodeURIComponent(JSON.stringify(config)));
// https://example.org/page?algolia_experiences_config=${encoded}

Parameters

Script URL parameters

| Parameter | Required | Description | | -------------- | -------- | -------------------------------- | | appId | Yes | Your Algolia Application ID | | apiKey | Yes | Your Algolia API Key | | experienceId | Yes | The ID of the experience to load |

Page URL parameters (preview bundle only)

| Parameter | Required | Description | | ---------------------------- | -------- | ----------------------------------- | | algolia_experiences_config | No | Base64-encoded JSON config override |

How it works

  1. The loader reads appId, apiKey, and experienceId from the script URL
  2. It calls the Algolia Experiences resolver to get the runtime bundle URL
  3. It injects the runtime script into the page
  4. It calls AlgoliaExperiences.run():
    • Production bundle: with no arguments
    • Preview bundle: with the decoded algolia_experiences_config from the page URL (if present)

The loader is lightweight and always fetches the latest compatible runtime version, so you never need to update the script tag.

Security

  • Use the production bundle on public sites. The preview bundle accepts configuration from the page URL, which could allow malicious links to manipulate displayed content.
  • Use a search-only API key with minimal permissions. The API key is visible in the page source.