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

@girs/st-18

v4.7.0

Published

GJS TypeScript type definitions for St-18

Readme

St-18

version downloads/week

GJS TypeScript type definitions for St-18 using ts-for-gir v4.7.0.

This package contains type declarations only. It ships no runtime code, so it adds nothing to your program and works with any bundler or none at all.

Install

npm install @girs/st-18

Any package manager works. The package has no dependencies beyond other @girs/* type packages.

What it exports

| Import | What you get | |---|---| | @girs/st-18 | the namespace as a default export, plus the ambient and global declarations | | @girs/st-18/ambient | only the gi:// module declarations | | @girs/st-18/import | only the imports.gi declarations | | @girs/st-18/st-18 | the namespace, without the side-effecting declarations |

Three ways to import

Which one you use depends on how you write imports elsewhere, not on your toolchain.

As a module

import St from '@girs/st-18';

As gi://

GJS resolves gi:// at runtime. To give it types, reference the package once, either from your entry point or from tsconfig.json:

import '@girs/st-18';
{ "include": ["@girs/st-18"] }

Then the runtime spelling type-checks:

import St from 'gi://St?version=18';

Referencing @girs/st-18/ambient instead pulls in these declarations alone. See ambient modules.

As imports.gi

GJS's global object works the same way, via @girs/st-18/import:

const St = imports.gi.St;

Building

The declarations need no build step. If you bundle, every bundler works, since there is no runtime code to resolve. The examples show working setups for several.

Other packages

Every pre-generated package is at gjsify/types.