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

@runtimescope/remix

v0.10.7

Published

RuntimeScope for Remix — one install, works in entry.client.tsx and entry.server.tsx

Readme

@runtimescope/remix

One install for full-stack Remix apps — browser + server in a single package.

npm install @runtimescope/remix

Setup

1. Environment

# .env
RUNTIMESCOPE_DSN=runtimescope://proj_xxx@localhost:6768/my-app

2. Client entry

// app/entry.client.tsx
import { initClient } from '@runtimescope/remix/client';
initClient();

// ...existing RemixBrowser hydrateRoot call

Expose the DSN to the browser via root.tsx loader (standard Remix pattern — see the Remix docs on "Exposing Environment Variables" for the full setup).

3. Server entry

// app/entry.server.tsx
import { initServer } from '@runtimescope/remix/server';
initServer();

// ...existing handleRequest export

4. (Optional) Wrap loaders/actions

import { withRuntimeScope } from '@runtimescope/remix/server';

export const loader = withRuntimeScope(async ({ request }) => {
  return json(await fetchData());
});

Subpath Exports

| Import | Use in | |--------|--------| | @runtimescope/remix | Shared utilities, types | | @runtimescope/remix/client | entry.client.tsx | | @runtimescope/remix/server | entry.server.tsx, loaders, actions |

Never import /server from a component file — Remix bundles the server code into the browser and it'll break.

Production Safety

If RUNTIMESCOPE_DSN is unset, the SDK is completely inert — no connection attempts, no errors, zero overhead.

License

MIT