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-monaco

v0.2.0

Published

Opt-in Monaco editor wrapper extracted from @asteby/metacore-starter-core. Apps without an embedded code editor avoid the ~2MB Monaco bundle entirely.

Readme

@asteby/metacore-starter-monaco

Opt-in Monaco editor wrapper extracted from @asteby/metacore-starter-core (v5+).

Use this only if your app needs an embedded code editor. Apps without an editor avoid the ~2MB Monaco bundle entirely (and the @monaco-editor/react peer dependency).

Install

pnpm add @asteby/metacore-starter-monaco @monaco-editor/react

Usage

import { CodeEditor } from '@asteby/metacore-starter-monaco'
import { useTheme } from '@asteby/metacore-starter-core' // or your local theme provider

function MyComponent() {
  const { theme } = useTheme()
  return (
    <CodeEditor
      value={code}
      onChange={setCode}
      language="json"
      theme={theme === 'dark' ? 'dark' : 'light'}
    />
  )
}

Props

| Prop | Type | Default | Description | | ------------------- | ----------------------------------------------------------------- | ----------- | ---------------------------------------------------- | | value | string | — | Editor content (controlled). | | onChange | (value: string \| undefined) => void | — | Fired on every keystroke. | | language | 'json' \| 'sql' \| 'javascript' \| 'typescript' \| 'plaintext' | 'json' | Monaco language mode. | | height | string \| number | '200px' | Editor height. | | readOnly | boolean | false | | | minimap | boolean | false | Show Monaco minimap on the right. | | theme | 'dark' \| 'light' | 'light' | Pass from your theme provider. | | disableValidation | boolean | false | Disable JSON schema validation markers. | | onDrop | (text: string) => void | — | Fired when content is dropped via drag-and-drop. |

Why a separate package?

@asteby/metacore-starter-core v4 declared @monaco-editor/react as a transitive cost for every consumer. Splitting Monaco out keeps starter-core lean for apps that never embed a code editor.