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/angular

v0.1.3

Published

Angular 22 standalone component for @larawag/core, the three.js view of a hypothetical planetary system.

Readme

@larawag/angular

npm

Angular 22 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/angular @larawag/core [email protected]

Yarn:

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

pnpm:

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

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

Usage

import { Component, input, viewChild } from '@angular/core';
import { StarSystemComponent } from '@larawag/angular';
import type { SystemInput } from '@larawag/core';

@Component({
  selector: 'app-preview',
  imports: [StarSystemComponent],
  template: `
    <div style="height: 480px">
      <larawag-star-system [system]="system()" scaleMode="compressed" (error)="warn($event)" />
    </div>
    <button (click)="view()?.setView('transit')">Transit view</button>
  `,
})
export class Preview {
  readonly system = input.required<SystemInput>();
  readonly view = viewChild(StarSystemComponent);

  warn(error: unknown) {
    console.warn(error);
  }
}

Inputs can also drive the view directly. Here a signal bound to [playing] plays and pauses it, with no reference to the component:

import { Component, input, signal } from '@angular/core';
import { StarSystemComponent } from '@larawag/angular';
import type { SystemInput } from '@larawag/core';

@Component({
  selector: 'app-stage',
  imports: [StarSystemComponent],
  template: `
    <div style="height: 480px">
      <larawag-star-system [system]="system()" scaleMode="true" [playing]="playing()" />
    </div>
    <button (click)="playing.set(!playing())">{{ playing() ? 'Pause' : 'Play' }}</button>
  `,
})
export class Stage {
  readonly system = input.required<SystemInput>();
  readonly playing = signal(true);
}

The inputs, outputs and methods match the React props: system (compared by value), scaleMode, showHabitableZone, rate, overlays and playing call the view's methods when they change; autoplay, minPlanetPixels, planetStyle, followOnClick and fallbackText rebuild the view; (tick), (error) and (followChange) are outputs; the component has play(), pause(), setTime(), setView(), resetView(), follow(), unfollow() and a view signal with the live view.

The host element is display: block; width: 100%; height: 100%, so size its parent. The view is created after the first render (nothing runs on the server) and destroyed with the component. The render loop runs outside Angular's zone, so apps that still use zone.js do not run change detection every frame; (tick) and (followChange) are emitted there too. Bind (tick) only when you need it, since each emit with a listener schedules change detection in a zoneless app.

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

Licence

MIT