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

tma-devtools

v0.1.0

Published

Dev-only interactive panel and rich Telegram client mock for Telegram Mini Apps. Strip from production.

Downloads

41

Readme

tma-devtools

Dev-only interactive panel and a rich Telegram client mock for Telegram Mini Apps. Emulate the user, drive the client, visualize the surface, watch the bridge, and resolve async flows — all without a real Telegram.

Part of tmakit.

HARD RULE: keep this in devDependencies and mount only behind import.meta.env.DEV. The mock is both dead weight and a security hole in production — it must never ship. When gated correctly, bundlers tree-shake it out entirely.

Install

npm i -D tma-devtools
npm i @telegram-apps/bridge   # or @tma.js/bridge (peer)

react / react-dom (>=18) are peer dependencies.

Usage

Set the mock up before your SDK initializes, then mount the panel behind the dev flag:

// tma-mock.ts — imported first, at the top of your entry
import { mockTelegramEnv, emitEvent } from '@telegram-apps/bridge';
import { createMock } from '@tmakit/core';

export const mock = createMock({
  bridge: { mockTelegramEnv, emitEvent },
  defaults: { platform: 'tdesktop', version: '8.0' },
});
import { DevtoolsPanel } from 'tma-devtools';
import { mock } from './tma-mock';

{import.meta.env.DEV && <DevtoolsPanel controller={mock} />}

The panel

  • log — every postEvent in both directions, timestamped, with payloads and a filter.
  • user — edit initData (name, username, language_code, premium, start_param) with premium / referral / RTL presets.
  • theme — switch light/dark, emitting theme_changed live.
  • viewport — height/width sliders, expanded/fullscreen toggles, safe-area inset editors.
  • buttons — visualize Main/Back/Secondary/Settings buttons and fire their presses; haptic indicator.
  • async — resolve pending popup / invoice / QR / clipboard / biometry requests.
  • platform — switch platform and client version, with a live feature-degradation preview.

The mock engine itself lives in @tmakit/core; this package is the UI on top of a MockController.

License

MIT