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

@zogien/native

v0.11.0-fork.1

Published

Community-maintained fork of Native SDK: TypeScript, Native markup, and native desktop tooling

Readme

@zogien/native

A community-maintained fork of the command-line tools for Native SDK. Create, build, test, and package native desktop applications with TypeScript and Native markup.

The default app core uses a checked TypeScript subset and compiles to native code. Native markup defines the interface, which the toolkit renders in OS windows. Apps can also use Zig cores or embed web content.

Install

npm install -g @zogien/native@fork

The native binary arrives as a per-platform optional dependency (@zogien/native-<platform>). Installation also downloads the exact scriptc release, verifies its checksum, and installs the matching compiler API and runtime packs into ~/.native/toolchains/scriptc/. This package carries the SDK source your apps build against, so native init and native dev work offline after installation. If npm install scripts are disabled, run node packages/core/scripts/install_scriptc.mjs from the installed CLI package before building. NATIVE_SDK_SCRIPTC_CACHE selects another toolchain cache directory. The pinned Zig toolchain is fetched into ~/.native/toolchains/ on first build unless a compatible zig is already on your PATH.

Use

native init my_app
cd my_app
native dev

The generated counter app uses src/core.ts for its model and updates, src/app.native for its view, and app.json for configuration. Existing app.zon manifests remain supported.

native dev reloads markup while preserving app state. Core changes rebuild and restart the app. Use native dev --core to exercise TypeScript logic under Node.js without a window, native check to validate the project, and native build for a release binary. Use --template zig-core with native init to create a Zig core instead.

When part of your product is the web, WebView surfaces coexist with the native canvas; web-frontend scaffolds (--frontend next, --frontend vite, and more) install their generated frontend dependencies automatically on first run.

Read the full guide at native-sdk.dev/quick-start.

Commands

| Command | Description | |---------|-------------| | native init [path] [--template <ts-core\|zig-core>] [--frontend <native\|next\|vite\|react\|svelte\|vue>] [--full] | Scaffold a new Native SDK app (TypeScript core + Native markup by default) | | native dev [dir] | Build and run the app (markup hot reload; managed frontend dev server when configured) | | native build [dir] | Build a ReleaseFast binary into zig-out/bin/ | | native test [dir] | Run the app's test suite | | native check [dir] | Validate src/**.native markup and app.json/app.zon against the model contract | | native markup check\|lsp | Check individual markup files, or serve diagnostics, completion, and hover to your editor | | native eject [dir] | Write an owned build.zig/build.zig.zon into the app | | native doctor | Check host environment, WebView, manifest, and CEF | | native validate | Validate app.json (or app.zon) against the manifest schema | | native package | Package the app for distribution | | native bundle-assets | Copy frontend assets into the build output | | native automate | Drive a running app: snapshots, widgets, assertions, screenshots, record/replay | | native skills list\|get <name> | List or print the built-in AI agent skills | | native version | Print the native version |

More

The full documentation is at native-sdk.dev — the quick start, TypeScript cores, native UI authoring, app model, components, testing, automation, capabilities, packaging, and platform support.

Native SDK is pre-1.0 and Apache-2.0 licensed; the fork source lives at github.com/zogien/native, based on vercel-labs/native.