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

@getblock/common

v0.2.15

Published

## Consuming this package

Readme

@getblock/common

Consuming this package

@getblock/core is a peer dependency (>=0.0.84 <0.1.0) — it is not bundled. The host application installs exactly one copy of core, and this package's components use that copy, so a fix in core reaches the modals without a release here.

What each build format needs:

| Format | Requirement | |--------|-------------| | ESM (import) | Nothing extra. @getblock/core and @getblock/core/styles resolve through the bundler; core's stylesheet is pulled in automatically. | | CJS / AMD | @getblock/core/styles appears in the dependency list, so the consumer's build must be able to load a CSS module id. | | UMD via browser globals | Provide window.GetblockCore and window.Vue, and include core's stylesheet yourself — e.g. <link rel="stylesheet" href=".../@getblock/core/dist/style.css">. In that path the stylesheet dependency is passed as null, so nothing loads it for you and components render unstyled if it is missing. |

Both first-party consumers (getblock-web, getblock-account) use the ESM build and need none of the UMD steps.

Import the stylesheets once in the app entry:

import '@getblock/core/styles';   // primitives + gb-* utilities
import '@getblock/common/styles'; // this package's own component styles

Vue 3 + TypeScript + Vite

This template should help get you started developing with Vue 3 and TypeScript in Vite. The template uses Vue 3 <script setup> SFCs, check out the script setup docs to learn more.

Recommended IDE Setup

Type Support For .vue Imports in TS

Since TypeScript cannot handle type information for .vue imports, they are shimmed to be a generic Vue component type by default. In most cases this is fine if you don't really care about component prop types outside of templates. However, if you wish to get actual prop types in .vue imports (for example to get props validation when using manual h(...) calls), you can enable Volar's Take Over mode by following these steps:

  1. Run Extensions: Show Built-in Extensions from VS Code's command palette, look for TypeScript and JavaScript Language Features, then right click and select Disable (Workspace). By default, Take Over mode will enable itself if the default TypeScript extension is disabled.
  2. Reload the VS Code window by running Developer: Reload Window from the command palette.

You can learn more about Take Over mode here.