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

@incajs/cli

v0.0.35

Published

Commands to develop, bundle, and package Incarnative.js apps.

Readme

@incajs/cli

The inca command for building and running Incarnative.js apps.

Install

npm i -D @incajs/cli

App entry

No entry point is required. Drop a src/App.vue and that's a whole app. Commit a src/main.mts, src/main.ts or src/main.js instead for full control over bootstrapping; it wins outright when both exist.

Commands

  • inca dev: watches your app and opens a window that applies each edit without a reload. dev.hmr: false reloads the whole app. See the HMR guide.
  • inca build: bundles your app for production, once, with no window opened.
  • inca package: builds your app, then packages it with the prebuilt host into a distributable application: a .app on macOS, a plain directory on Linux (other platforms aren't supported yet).
  • inca config: prints the settings the host applies to your app, such as its window size, as JSON.

When running inca, it will automatically try to resolve a config file named inca.config.ts inside your app's root (other JS/JSON extensions are also supported), for app metadata and build settings:

import { defineConfig } from "@incajs/cli/config";

export default defineConfig({
  // the app's display name
  productName: "Click Counter",
  // macOS's CFBundleIdentifier or equivalent
  identifier: "com.example.click-counter",
  // the app's icon file
  icon: "assets/icon.icns",
});

An identifier should be world-unique, so inca package prints a note when it falls back to the generated one rather than using it silently.

On macOS, inca dev launches the app under its productName, icon and identifier, so the Dock and the menu bar show the same app they will once it is packaged.

Requirements

A prebuilt binary is pulled in automatically as a platform-specific optional dependency. Neither Cargo nor Rust are needed. See Host binary for per-platform support.

Set INCA_HOST_BIN to use a specific binary instead, e.g. on a platform with no published one yet, or a custom build.

How it works

inca dev/build/package bundle your app with Vite, then (for dev and package) launch and supervise the host, the native runtime that renders it, as a child process.