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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@in8sync/spherical-cli

v1.0.3

Published

CLI tool for creating and building external React components for Spherical BRM for Netsuite.

Readme

In8Sync Spherical CLI

A command-line tool for creating and building external React components that you can use inside the Spherical UI Builder.

All components are built for the Puck editor, so you need to get familiar with this library first, since all components need to follow the same structure and configuration requirements.

Installation

# Install globally
npm install -g @in8sync/spherical-cli

# Or use with npx
npx spherical-cli --help

Commands

init <project-name>

Initialize a new external components project with a Vite + React setup.

spherical-cli init my-components
cd my-components

This creates:

my-components/
├── package.json
├── vite.config.js
├── components.json
└── src/
    └── ExternalButton.jsx

build

Build the components using Vite. Must be run inside a project directory.

cd my-components
spherical-cli build

This will build your components and put them in the dist/ folder. You then need to upload them through the client admin dashboard, and they will be available for you to use in the Spherical UI Builder.

Project Structure

The generated project follows this structure:

  • package.json - Project dependencies and scripts
  • vite.config.js - Vite configuration for building ES modules
  • components.json - List of available components (you must add new components here)
  • src/ - Source directory for components
    • ExternalButton.jsx - Example button component

Important: Every time you add new components, you need to add them to the components.json file.

Usage

  1. Initialize a project:

    spherical-cli init my-project
    cd my-project
  2. Develop your components:

    • Edit files in src/
    • Add new components to components.json
  3. Build for production:

    spherical-cli build
  4. Deploy your components:

    • Upload the dist/ folder contents through the admin dashboard
    • Components will be available in the Spherical UI Builder

Component Development

Each component should:

  • Export a default React component
  • Export a puckConfig object with Puck editor configuration

For more details on configuration options and available fields, see the Puck documentation.

Remember: Every new component must be added to the components.json file to be recognized by the system.