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

cds-spreadsheetimporter-plugin

v1.0.3

Published

Spreadsheet importer as CAP plugin

Readme

cds-spreadsheetimporter-plugin

This is a plugin for the CAP framework that allows you to import data from spreadsheets into your CAP project.

Release Process

This project uses release-it to automate version management and package publishing. The release workflow is configured through GitHub Actions and can be triggered in two ways:

Manual Release

  1. Go to the GitHub repository's "Actions" tab
  2. Select the "Release" workflow
  3. Click "Run workflow"
  4. You can either:
    • Leave the version field empty for automatic versioning based on conventional commits
    • Specify a specific version (e.g., "1.2.0")

Local Release (for maintainers)

If you prefer to release from your local machine:

  1. Ensure you have the necessary credentials:
    • NPM_TOKEN for publishing to npm
    • GITHUB_TOKEN for creating GitHub releases
  2. Run one of the following commands:
    npm run release              # For automatic versioning
    npm run release X.Y.Z        # For specific version

What happens during release?

The release process will:

  1. Determine the next version number (based on conventional commits or manual input)
  2. Update the package.json version
  3. Generate/update the CHANGELOG.md file
  4. Create a git tag
  5. Push changes to GitHub
  6. Create a GitHub release with release notes
  7. Publish the package to npm

The release configuration uses the Angular conventional commit preset for changelog generation and requires commit messages to follow the conventional commits specification.