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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@rbxts/metrik

v0.0.3

Published

SDK for https://metrik.app

Downloads

2

Readme

Metrik SDK alpha

GitHub release (latest by date) GitHub issues GitHub pull requests GitHub Workflow Status

Warning The Metrik API is NOT currently online. Metrik and the SDK will not work at the moment. Additionally, some parts of the codebase will just straight up not work.

This is the Roblox SDK for Metrik, the automated LiveOps toolkit for Roblox. This module is still in heavy development, is not feature complete, subject to breaking changes, and is not recommended for production use.

Install options include:

  • Plugin (coming soon)
  • Wally
  • .rbxm/.rbxmx
  • roblox-ts

Installation

via Wally

You must have wally installed. Learn more about Wally by Uplift Games here.

wally install metrik-tech/metrik

via .rbxm/.rbxmx

Download from GitHub releases and insert into Studio or Rojo. Releases can be found here.

via roblox-ts

Note This is *NOT* to be used with regular Luau. This is only for use with roblox-ts, a TypeScript-to-Luau compiler. Learn more about roblox-ts and whether or not it's the right fit for your project here.

# npm
npm install @rbxts/metrik

# yarn
yarn add @rbxts/metrik

# pnpm
pnpm add @rbxts/metrik

Usage

You need to initalize Metrik on both the client and the server. However, config options only need to be passed on the server (This is subject to change).

Server

TypeScript

// any server script (file.server.ts)
import Metrik from "@rbxts/metrik";

const metrik = new Metrik({
    token: "your-token-here",
    options: {
        debug: true
    }
})

Lua

-- any server script (file.server.lua)
-- or a script in ServerScriptService
local Metrik = require(path.to.Metrik)

local metrik = Metrik.new({
    token = "your-token-here",
    options = {
        debug = true
    }
})

Client

TypeScript

// any client script (file.client.ts)
import Metrik from "@rbxts/metrik";

new Metrik();

Lua

-- any client script (file.client.lua)
-- or a LocalScript (preferably in StarterPlayerScripts)

local Metrik = require(path.to.Metrik)

Metrik.new()

Options

interface IOptions {
    debug?: boolean; // defaults to false. logs internal events and errors to output if true
    logMetrikMessages?: boolean; // defaults to false. logs messages outputted by the SDK to the dashboard if true 
    apiBase?: string; // defaults to https://api.metrik.app. in most cases, you shouldn't need to change this
}

API

metrik.log(message: string, data: unknown): Promise<void> SERVER ONLY

Logs a message to the Metrik dashboard with extra details. Internally throws a print.

metrik.error(message: string, data: unknown): Promise<void> SERVER ONLY

Logs an error to the Metrik dashboard with extra details. Internally throws a warn.

metrik.crash(message: string, data: unknown): Promise<void> SERVER ONLY

Logs a crash to the Metrik dashboard with extra details. Internally throws an error, which stops the thread where it was called AFTER the crash is logged.

metrik.warn(message: string, data: unknown): Promise<void> SERVER ONLY

Logs a warning to the Metrik dashboard with extra details. Internally throws a warn.