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

movable_tool_box

v1.0.6

Published

Utility to add SE Packages from the CLI

Readme

Movable Tool Box

This package aims to make adding tools to custom apps easier by providing a CLI for adding SE packages.

Currently, the Movable Tool Box works with the following SE Packages:

Rating Tool

Every Mundo

Map Tool

Usage

Run npm i movable-tool-box or yarn add movable-tool-box from the root of the app. Once this package is installed, run add-tool <tool name> from anywhere in the app.

Current Mappings:
  'rating' -> Rating Tool
  'map' -> Map Tool
  'mundo' -> Every Mundo Tool

The add-tool command will do seven things:

  1. Install the tool as a dependency in the package.json
  2. Update the app-manifest.yml file with the appropriate properties under tools and properties
  3. Add any assets needed to the app/img directory
  4. Register the tool in the app/js/app.js file
  5. Inject boilerplate code in the app/js/properties/index.js file
  6. Add any necessary files to app/js/tools
  7. Add any necessary files to app/js/components

Contributing

Adding tools to the Movable Tool Box is easy. Clone this GitHub repo, make a branch with the name of the tool you're adding and add the following:

  1. Add any necessary assets to the src/assets directory.
  2. Add a file named <toolName>Tool.js in the src/templates directory.
  3. The template file should have seven array declarations. At the bottom of this README is the template for the rating tool. Note that the spaces in the strings should be made with spaces, not tabs. This will preserve their spacing in the injected code. If any declarations are not needed, set the variable to null. Declare an object that contains all of the declaration variables and export it.
  4. In src/editUtils.js, import your new template at the top of the file. Then add a case in the switch statement on the getTemplate function. The case will be the tool name that gets called in the CLI, the result should be returning your newly imported template object.
  5. Add any needed files for the tools or components directory in src/files.
  6. Update README to include the mapping of tool name to the tool it's installing, plus a link to the SE Packages page for that tool.

Once it's done, submit a PR and I'll update the package.

Known Issues

If the app/js/properties/index.js file is empty except for the boilerplate created on a brand new app, the injected code will appear outside of the appProperties function. This is avoidable by putting a comment in the function to preserve the line break.

Template File Example

const toolDeclaration = [
  "   - type: productRating",
  "     name: productRating",
  "     label: Rating",
  "     icon: twitter-favorite",
  "     defaults:",
  "       text:",
  "       width: 150",
  "       height: 14",
  "       backgroundColor: transparent",
  "     dynamic_fields:",
  "       - type: api",
  "         label: Rating Data",
  "         description: Rating Data",
  "         name: dynamicProperty",
  "         allow_static_option: true",
  "         class_names: rating"
];

const propertyDeclaration = [
  "    - name: starRating",
  "      label: Star Rating Data",
  "      description: Star Rating",
  "      properties:",
  "        - name: app.rating",
  "          label: Stars",
  "          description: Stars",
  "          type: api",
  "          context_options:",
  "            - type: text",
  "              name: ratingIndex",
  "              label: Item Index",
  "              description: Item Index",
  "              value: '1'"
];

const toolRegisterDeclaration = [
  "    this.registerTool('productRating', ratingTool);"
];

const importDeclaration = [
  "import { ratingTool } from '@movable-internal/rating-tool';",
  "import '@movable-internal/rating-tool/package-manifest.yml';"
];

const propertiesJSDeclaration = [
  "  app.setProperty('app.rating', ({ getProperty }) => {",
  "    const { averageRating } = getProperty('parseData');",
  "    return {",
  "      rating: averageRating,",
  "      maxRating: 5,",
  "      fullStar: './app/img/star.png',",
  "      halfStar: './app/img/half.png',",
  "      emptyStar: './app/img/empty.png',",
  "      width: '15',",
  "      height: '13'",
  "    };",
  "  });"
];

const assets = ["empty.png", "half.png", "star.png"];

const dependencies = ["@movable-internal/rating-tool"];

const toolFiles = null; // ['myToolFile.js']

const componentFiles = null; // ['myComponentFile.js']

const ratingToolTemplate = {
  toolDeclaration,
  propertyDeclaration,
  toolRegisterDeclaration,
  importDeclaration,
  propertiesJSDeclaration,
  dependencies,
  assets
};

module.exports = {
  ratingToolTemplate
};