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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@blockly/suggested-blocks

v5.0.0

Published

A plugin that adds toolbox panes with suggested blocks based on the user's past usage of blocks.

Downloads

257

Readme

@blockly/suggested-blocks Built on Blockly

A Blockly plugin that suggests blocks for the user based on which blocks they've used already in the workspace.

Installation

Yarn

yarn add @blockly/suggested-blocks

npm

npm install @blockly/suggested-blocks --save

Usage

import * as Blockly from 'blockly/core';
import * as SuggestedBlocks from '@blockly/suggested-blocks';

const toolbox = {
  kind: 'categoryToolbox',
  contents: [
    {
      kind: 'category',
      name: 'My Category',
      contents: [
        /* your category contents */
      ],
    },
    {
      kind: 'category',
      name: 'Frequently Used',
      custom: 'MOST_USED',
      categorystyle: 'frequently_used_category',
    },
    {
      kind: 'category',
      name: 'Recently Used',
      custom: 'RECENTLY_USED',
      categorystyle: 'recently_used_category',
    },
  ],
};

// Inject Blockly.
const workspace = Blockly.inject('blocklyDiv', {
  toolbox: toolbox,
});

// Initialize the plugin
SuggestedBlocks.init(workspace);

API

  • init: Initializes the suggested blocks categories in the toolbox. Takes several arguments:
    • workspace: The workspace to use the plugin with. If you have multiple workspaces, you need to register the plugin for each workspace separately, and the stats will be tracked separately.
    • numBlocksPerCategory (optional): The maximum number of blocks to show in each category. Defaults to 10.
    • waitForFinishedLoading (optional): Whether to wait for the Blockly.Events.FinishedLoading event before taking action on any new BlockCreate events. If you disable event firing while you load the initial state of the workspace, you'll need to set this to false, or the plugin will never place blocks in either category. By default, this value is true, so that events fired while loading initial serialized state do not affect the statistics. If you leave this value as true, you need to ensure the FinishedLoading event is always fired; if you don't call Blockly.serialization.workspaces.load when there is no saved state to load, you'll need to fire it yourself for this plugin to work correctly.

License

Apache 2.0