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

@asteby/metacore-starter-core

v8.0.0

Published

Metacore starter core — shared providers, stores, hooks y context que consumen las apps Vite+React que embeden el kernel.

Readme

@asteby/metacore-starter-core

Internal scaffolding shared by the official Metacore Vite + React starter and a small number of internal apps. It is not published to npm ("private": true in package.json) and is excluded from the Changesets publish pipeline.

If you are building a Metacore app, start from @asteby/create-metacore-app instead — it scaffolds a project that depends on the public @asteby/metacore-* packages directly, without going through this internal layer.

What lives here

The package re-exports curated subsets of:

  • lib/ — small utilities used across the starter templates.
  • components/ui/ — shadcn/ui primitives in their canonical form, kept in sync with @asteby/metacore-ui.

It exists so the templates/ shipped by @asteby/create-metacore-app can pin a single version of the starter scaffolding while the public packages evolve at their own pace.

Build

pnpm --filter @asteby/metacore-starter-core build

Produces an ESM + CJS bundle via Vite library mode and .d.ts files via tsc. The build runs in CI but is excluded from pnpm release because the package is private.