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

@larawag/react

v0.1.3

Published

React 19 component and hook for @larawag/core, the three.js view of a hypothetical planetary system.

Readme

@larawag/react

npm

React 19 bindings for @larawag/core, which draws a hypothetical single-star planetary system with three.js. Everything drawn is hypothetical: the look is a guess from a few numbers, never a claim about a real planet's composition or surface.

Install

npm:

npm install @larawag/react @larawag/core [email protected]

Yarn:

yarn add @larawag/react @larawag/core [email protected]

pnpm:

pnpm add @larawag/react @larawag/core [email protected]

@larawag/core, react (19) and three (>=0.186.0 <0.187.0) are peer dependencies.

Usage

import { useRef } from 'react';
import type { SystemInput } from '@larawag/core';
import { StarSystem, type StarSystemHandle } from '@larawag/react';

const Preview = ({ system }: { system: SystemInput }) => {
  const view = useRef<StarSystemHandle>(null);

  return (
    <div style={{ height: 480 }}>
      <StarSystem system={system} scaleMode="compressed" ref={view} onError={(e) => console.warn(e)} />
      <button onClick={() => view.current?.setView('transit')}>Transit view</button>
    </div>
  );
};

The component renders one div with width: 100%; height: 100%, so size its parent. It creates the view after mount and destroys it on unmount, so it is safe under StrictMode and renders an empty div on the server. The file starts with 'use client' for the Next.js App Router.

useStarSystem(containerRef, system, props) mounts the view in an element you render yourself and returns the same handle the component's ref gives you:

import { useRef } from 'react';
import type { SystemInput } from '@larawag/core';
import { useStarSystem } from '@larawag/react';

const Stage = ({ system }: { system: SystemInput }) => {
  const container = useRef<HTMLDivElement>(null);
  const view = useStarSystem(container, system, { scaleMode: 'true' });

  return (
    <section>
      <div ref={container} style={{ height: 480 }} />
      <button onClick={() => view.pause()}>Pause</button>
    </section>
  );
};

Avoid setting React state from onTick on every frame; the clock overlay already shows the time.

The system input, options and view methods are documented in the main README.

Licence

MIT