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

@rubedo/devkit

v0.1.2

Published

A blank schematics

Readme

devkit schematics usage

Install angular schematics globally

yarn global add @angular-devkit/schematics-cli

Install rubedo schematics to your project

yarn add -D @rubedo/schematics

From your project directory run

schematics @rubedo/devkit:devkit

You will get a CLI checklist, a multi-select from which you can check with Space button tools that you want to be scaffolded. You can select multiple tools to be scaffolded at once. After you've selected desired tools for scaffolding, hit Enter. Your package.json and / or project file structure will be updated depending on which tools you chose. You will get a console output stating what was updated and how (package.json: scripts, dependencies, devDependencies / project file structure).

Getting Started With Schematics

This repository is a basic Schematic implementation that serves as a starting point to create and publish Schematics to NPM.

Testing

To test locally, install @angular-devkit/schematics-cli globally and use the schematics command line tool. That tool acts the same as the generate command of the Angular CLI, but also has a debug mode.

Check the documentation with

schematics --help

Unit Testing

npm run test will run the unit tests, using Jasmine as a runner and test framework.

Publishing

To publish, simply do:

npm run build
npm publish

Building and testing locally

After cloning the project:

npm i --ignore-scripts

You can publish the schematic locally to test against any Nx workspace using verdaccio:

npm i -g verdaccio
verdaccio  // to start the private local npm registry
  1. Publish the schematic to verdaccio with the following:
npm run build
npm publish --registry http://localhost:4873
  1. Setup a fresh Nx workspace to test with:
create-nx-workspace myworkspace
  1. Open the workspace and add .npmrc to root with the following:
@nstudio:registry=http://localhost:4873
  1. You can now install your schematic changes with:
npm i @nstudio/schematics -D --registry http://localhost:4873 --force

Anytime you make further changes to the schematic just rebuild/republish:

npm run build
npm publish --registry http://localhost:4873
// then repeat Step #4 to install latest 

If you get this error:

npm ERR! code EPUBLISHCONFLICT
npm ERR! publish fail Cannot publish over existing version.
npm ERR! publish fail Update the 'version' field in package.json and try again.
npm ERR! publish fail 
npm ERR! publish fail To automatically increment version numbers, see:
npm ERR! publish fail     npm help version

You can simply unpublish and publish like this:

npm unpublish --registry http://localhost:4873 --force
npm publish --registry http://localhost:4873

Unit Tests

npm test

All tests must pass. Please add tests for any new functionality.


In order to test schematics locally in debug mode (without writing files) run

schematics .:schematicName

or in normal mode

schematics .:schematicName --debug=false