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

@editorjs/create-tool

v0.1.3

Published

Editor.js Tool single command generator

Downloads

4

Readme

🚧 Development in progress 🚧

Editor.js Tool — starter kit package

Single command helper to generate a Tool template.

Usage

Use create command to generate Tool's starter kit.

npm create @editorjs/tool <tool-name>
yarn create @editorjs/tool <tool-name>

Development

New project files will be used from template folder. You can work in this folder as in generated project: upgrade dependencies, add new files, run build and dev commands.

In templates there is a variable that will be replaced with user's input:

  • VAR_TOOL_NAME — tool name

Local testing

To test the package locally, you have to create a symlink to the global node_modules folder. Use the package to generate a new tool. And then you need to unlink local package.

Linking

Run the following command in the root of this package repository:

npm link
yarn link

In the folder where you want to create a new tool, link the local package:

npm link @editorjs/create-tool
yarn link @editorjs/create-tool

Usage

Use this tool as usual:

npm create @editorjs/tool <tool-name>
yarn create @editorjs/tool <tool-name>

Unlinking

To unlink the local package run the following in tool's parent folder where I had to link it earlier:

npm unlink @editorjs/create-tool
yarn unlink @editorjs/create-tool

And then unlink the package in the root of this package repository:

npm unlink @editorjs/create-tool
yarn unlink @editorjs/create-tool