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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fresk-web-sdk

v0.3.4

Published

Error reporting and monitoring for web applications

Readme

Fresk Web SDK

Getting Started

Prerequisites

  • Node.js 16.x or higher
  • Bun 1.x or higher

Installation

To install dependencies:

bun install

To test the SDK:

bun run test

To build the SDK:

bun run build

Usage

Importing the SDK

Import the SDK in your project:

import FreskWebSDK from "fresk-web-sdk/core";

Initializing the SDK

The SDK must be initialized before it can be used.

Initialize the SDK in your project:

const freskSDK = new FreskWebSDK({
  appId: "your_app_id",
  appKey: "your_app_key",
  appName: "your_app_name",
  endpoint: "your_fresk_server_url",
  version: "your_app_version",
  environment: "your_app_environment",
});

freskSDK.init();

The recommended way is to create a new instance of the SDK, and then initialise it in your main entry point. Then you can use the SDK anywhere in your application by importing it and calling the identify or any other method. eg.

// fresk-instance.js
import FreskWebSDK from "fresk-web-sdk/core";

const freskSDK = new FreskWebSDK({
  appId: "your_app_id",
  appKey: "your_app_key",
  appName: "your_app_name",
  endpoint: "your_fresk_server_url",
  version: "your_app_version",
  environment: "your_app_environment",
});

export default freskSDK;
// main.js
import freskSDK from "./fresk-instance.js";

freskSDK.init();
// login.js
import freskSDK from "./fresk-instance.js";

const afterLogin = (email) => {
  freskSDK.identify(email);
};

SSR (Server-Side Rendering)

The SDK depends on the window object, which is not available in server-side rendering (SSR) environments. Support for SSR is planned for a future release.

Source Maps

You can configure the SDK to send source maps to the Fresk server for improved debugging experience. Currently we only support Rollup/Vite, but we plan to support other frameworks in the future.

Follow these steps to enable source maps:

  1. in your vite.config.js file, add the following plugin:
import { FreskPluginVite } from "fresk-web-sdk/vite";

const freskConfig = {
      appId: "your_app_id",
      appKey: "your_app_key",
      appName: "your_app_name",
      endpoint: "your_fresk_server_url",
      version: "your_app_version",
      environment: "your_app_environment",
      verbose: true, // optional
    }
    
export default defineConfig({
  plugins: [
    FreskPluginVite(freskConfig), // add to vite plugins
  ],
});
  1. In your vite.config.js file, enable source maps:

...

export default defineConfig({
  plugins: [
    FreskPluginVite(freskConfig), // add to vite plugins
  ],
  // enable sourcemaps
  build: {
    sourcemap: "true",
  },
});

Then when you build, it will send the source maps to the Fresk server.

Identifying Users

Identify users by their email address:

freskSDK.identify("[email protected]");

Resetting the Session

Reset the session:

freskSDK.reset();

Capturing Errors

The SDK automatically captures errors and sends them to the Fresk server for analysis.