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

@banch0u/core-project-test-repository

v2.2.0

Published

Shared core features for all projects

Readme

📦 @banch0u/core-project-test-repository – Development & Deployment Guide

✨ Live Development Setup

To develop and test changes in the core package live within another project (e.g., docflow, hr, contract, account and etc.), follow these steps:


📌 Before You Start

Ensure that Yalc is installed globally on your system:

npm install -g yalc

💠 Step 1: Start the Core Package in Watch Mode

This will watch your src/ directory for changes, rebuild the dist/ folder, and automatically push updates to .yalc:

npm run dev

💠 Step 2: In Your Main Project (Consumer App)

Important: Before executing this step, make sure your main project's dev server is stopped.

✅ a. Add the Core Package via Yalc

yalc add @banch0u/core-project-test-repository

This copies the current dist/ folder into your project's .yalc directory and updates your package.json.

🔗 b. Link the Core Package

yalc link @banch0u/core-project-test-repository

This creates a symlink to the core package. Now, all changes from the npm run dev watcher will reflect automatically when you start your project's dev server again (npm start).


⚠️ Important Notes

  • Your package.json will temporarily contain:

    "@banch0u/core-project-test-repository": "file:.yalc/@banch0u/core-project-test-repository"
  • This file path will break production builds or CI/CD pipelines.

  • Before deploying or committing:

    • Manually delete the line above from your package.json.
    • Replace it by installing the latest package from npm:
    npm install @banch0u/core-project-test-repository@latest

📦 Publishing to NPM

1. Build the Package

npm run build

This will transpile your src/ folder into the dist/ folder.

2. Bump Version

Use npm version to update the package version according to the type of change:

  • Patch (small fix): npm version patch1.0.0 → 1.0.1
  • Minor (new feature, backward compatible): npm version minor1.0.0 → 1.1.0
  • Major (breaking changes): npm version major1.0.0 → 2.0.0

3. Publish to NPM

npm publish

Your changes will now be available on the npm registry. Consumers can install the latest version via:

npm install @banch0u/core-project-test-repository@latest

Happy coding 💻🚀