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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@basaldev/blocks-catalog-service

v5.2.5

Published

Service for managing product catalog and categories.

Readme

blocks-catalog-service


Overview

TODO

🏗 Project Structure

.
├── .github                
├── .husky                 # husky settings - @basaldev/lint-staged-config
├── .vscode                # vscode settings
├── .yarn                  # yarn binary, config and project dependencies
├── coverage *             # jest coverage report
├── dist *
├── docs
│   ├── assets             # documentation related assets
│   └── reference          # api docs
├── src
│   ├── adapter
│   ├── test
│   └── index.ts
├── .eslintignore
├── .eslintrc.js            # @basaldev/eslint-config
├── .gitignore
├── .nvmrc
├── .pnp.cjs                # yarn config
├── .pnp.loader.mjs         # yarn config
├── .prettierignore
├── .prettierrc.json        # @basaldev/prettier-config
├── .yarnrc.yml             # yarn config
├── cspell.config.js        # @basaldev/cspell-config
├── .yarnrc.yml             # yarn config
├── jest.config.js          # @basaldev/jest-preset
├── package.json
├── README.md
├── tsconfig.json           # @basaldev/tsconfig
└── yarn.lock

* Not tracked by git

🔰 Setup

Get NPMJS private token for nodeblocks

  1. Please contact @basal-gen or @basal-luke for getting the token
  2. Add to your local environment - .zshrc .bashrc etc
export NODEBLOCKS_DEV_TOKEN=__INSERT_YOUR_TOKEN_HERE__

Install NVM

Install Yarn (Global)

Yarn must be installed globally for the project's NodeJS version. This should be done so using the command below.

nvm use && npm install -g yarn

Install Husky 🐺

yarn husky install

⚠️ IMPORTANT: Only use the yarn command install or run scripts. Do not use npm run xxx

🪄 Usage

Run typescript compiler

yarn start

Run debug server on default port: 9339.

  • Requires yarn start to be running in a separate session
  • Port should be updated to avoid conflicts with other projects package.json > scripts > debug
yarn debug

Run unit tests

docker compose up
yarn test

Installing packages

yarn add <package> | yarn add <package> -D

DB Migration

DB need Atlas Mongodb DB need create a Search index for search use (name is product_free_text_search_index)

{
  "analyzer": "lucene.kuromoji",
  "searchAnalyzer": "lucene.kuromoji",
  "mappings": {
    "dynamic": true,
    "fields": {
      "description": {
        "analyzer": "lucene.kuromoji",
        "ignoreAbove": 18,
        "searchAnalyzer": "lucene.kuromoji",
        "type": "string"
      },
      "name": {
        "analyzer": "lucene.japanese",
        "ignoreAbove": 20,
        "searchAnalyzer": "lucene.japanese",
        "type": "string"
      }
    }
  },
  "storedSource": true
}

⚡️ Special Notes for VSCode Users

📐 Required Extensions

Please ensure the following extensions are installed:

  • arcanis.vscode-zipfs
  • dbaeumer.vscode-eslint
  • seatonjiang.gitmoji-vscode
  • henrynguyen5-vsc.vsc-nvm (optional)

🛠 Workspaces

The kit uses vscode workspaces for vscode project settings:

  • All common vscode project settings should be specified in the .vscode/${project_name}-workspace file.
  • Personal user settings should be added to .vscode/settings.json (gitignored)
  • ⚠️ You must open this project as a workspace in vscode This can be done by clicking the workspace file while in vscode, or by using File > Open workspace from file.

🪛 TypeScript

When prompted asking which typescript VSCode should use, it's very important that you choose the local project version located at .yarn/sdks/typescript/...

💅 Prettier

If you have the prettier extension installed, please disable it for this project. ts-kit uses eslint to execute prettier, so having prettier enabled in vscode will cause conflicts and strange behavior.

🤖 Format on Save (optional)

Add the following code to your .vscode/settings.json will automatically fix all eslint errors whenever you save a file.

  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  }

🚀 Package Deployment

This library uses github registry to publish private npm package. For detailed instructions see here

💡 Note: that npm is used for version & publish commands

1. Bump version

npm version ${VERSION}

2. Build Package

yarn build

3. Publish Package

npm publish --tag=latest | experimental

Then go to github https://github.com/basaldev/backend-sdk/packages to check published packages.