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

@eclipse-scout/releng

v26.2.1

Published

Release engineering module for Eclipse Scout

Readme

Eclipse Scout - Releng

Contains release engineering scripts for the Eclipse Scout framework.

Deploy

  1. Check that there are no *.js files in the module. If there are old build artifacts: remove them first.
  2. Update version in package.json: set to a unique new version without -snapshot suffix.
  3. Run tests using npm script npm run test.
  4. Build using npm script npm run build.
  5. Deploy to a local registry to test the new package: npm publish --registry http://127.0.0.1:4873/.
  6. If all is fine: Deploy to real registry: npm publish (requires corresponding access token in your .npmrc).

Version Update

  1. Align the following dependencies with the ones of the new pnpm version (check version by git checkout of the corresponding tag):
    1. @pnpm/*
    2. realpath-missing as specified by pnpm
    3. normalize-path as specified by pnpm
  2. Use the newest compatible version of typanion (check version constraint of @pnpm/npm-lifecycle > @yarnpkg/shell > clipanion declaring the peer)
  3. Update the engines in the package.json
  4. In this module search for Inspired by https://github.com/pnpm/pnpm and check the history of the declared files for changes since the last version. Merge them as necessary.