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

@bostonuniversity/block-imports

v0.1.4

Published

Block Imports for BU Plugins and Themes

Readme

BU Block Imports

Standardized set of components, hooks, and utilities that can be used within WordPress blocks.

In Development: This is just starting (March 2025) and it should be assumed that nothing actually works yet. Bug reports, feature requests, questions, and pull requests are welcome.

Installation

  1. Run npm i @bostonuniversity/block-imports -D within your WordPress theme or plugin.
  2. Within your block editor code, import the relevant component(s) e.g. import { ContentPicker } from '@bostonuniversity/block-imports';

Components

Components are independent and reusable bits of code. They serve the same purpose as JavaScript functions, but work in isolation and return HTML.

These should be named in PascalCase without a BU namespace. They should use the .mjs extension.

Hooks

These are React Hooks, not WordPress Hooks. Hooks allow function components to have access to state, lifecycle methods, and other React features.

These should be named in camelCase without a BU namespace. They should use the .mjs extension.

Utils

These are just your standard garden variety javascript functions. They don't need all the features that hooks have.

These should be named in camelCase without a BU namespace. They should use the .mjs extension.


Development

Each folder should contain a README.md file explaining the purpose and usage of the component/hook/util.

Debugging

There is no build for this package. You can debug it though by running npx wp-scripts build index.js and ensure all paths can be resolved.

Publishing & Release Process

This package is managed through NPM. It can be found here: https://www.npmjs.com/package/@bostonuniversity/block-components

This repo has an action that will run whenever a new release is created.

To learn more about how NPM is managed for BU projects, please read https://developer.bu.edu/webteam/developer/vcs/npm-javascript-packages/

NOTE: you should verify that the package JSON file includes the following to make publishing easier:

"publishConfig": {
    "access": "public"
  }