open-index/open-npm huggingface dataset:
npm package: @shelfforce/cli
Description: Turn shelf photos into structured data from your terminal.
Latest version: 0.1.2

# Shelfforce CLI

Turn shelf photos into structured data from your terminal.

## Install

```bash
npm install -g @shelfforce/cli
```

## Quick Start

### 1. Authenticate

```bash
sf login
```

This opens your browser to sign in and authorize the CLI. Your key is stored locally.

For CI or non-interactive environments:

```bash
sf login --key sf_live_a1b2c3d4...
```

Or set an env var:

```bash
export SF_API_KEY=sf_live_a1b2c3d4...
```

### 2. Check your account

```bash
sf whoami        # Show email, plan, credits
sf usage         # Detailed credits, rate limits, batch max
```

### 3. Analyze a shelf image

```bash
# URL
sf run https://example.com/shelf.jpg

# Local file
sf run ./shelf-photo.jpg

# Directory (batch)
sf run ./store-photos/

# Text file with URLs (one per line)
sf run urls.txt

# With tracking ID
sf run https://example.com/shelf.jpg --external-id customer-123

# Save results to ~/Downloads/
sf run https://example.com/shelf.jpg --save

# JSON output
sf run https://example.com/shelf.jpg --json
```

### 4. Browse your data

```bash
sf places list
sf tasks list --status pending
sf inventory list --brand "Coca-Cola"
sf accounts list --type brand
sf orders list
```

### 5. Run reports

```bash
sf reports share-of-shelf --days 30
sf reports compliance --place-id pl_abc123
sf reports store-performance --days 30
```

### 6. Interactive shell

```bash
sf
```

Type commands without the `sf` prefix. Use `/` to see all commands, `/quit` to exit.

## Profiles

```bash
sf login --name production
sf login --name staging

sf profiles
sf profile:use staging
```

## Environment Variables

| Variable | Description |
|----------|-------------|
| `SF_API_KEY` | API key (overrides stored auth) |
| `SF_API_URL` | App URL for browser login (for dev environments) |

## All Commands

```
sf login              Authenticate via browser
sf logout             Remove stored auth
sf whoami             Show current auth
sf profiles           List profiles
sf profile:use        Switch profile
sf usage              Credits, rate limits
sf run                Analyze image (URL, file, directory, or .txt of URLs)
sf places             Manage stores
sf tasks              Manage tasks
sf inventory          Manage catalog
sf accounts           Manage accounts
sf orders             Manage orders
sf webhooks           Manage webhooks
sf members            Manage team
sf reports            Run reports
```

Run `sf <command> --help` for options.
npm package: @shelfjs/health-checks
Description: ## Problem
Latest version: 2.0.1

# Health Checks

## Problem

Imagine a huge application with a bunch of internal services, you are tasked with changing the pipe in one of the controllers. Pipe has nothing to do with the database or Kafka. In order to run the application and test the pipe, you will need to bring up the database and all external services. Not very convenient, huh?

How to run an application that does not depend on a database, kafka or any other internal services? How to get service connection status from an application?

## Solution

Do not terminate the application if the connection to internal services failed. The application should work even if it is not connected to the database

> A health check represents a summary of health indicators. A health indicator executes a check of a service, whether it is in a healthy or unhealthy state. A health check is positive if all the assigned health indicators are up and running.

In this example, I'm using Prisma ORM and built indicator above prisma connection. First, install `@shelfjs/health-checks` package

```bash
npm i --save @shelfjs/health-checks
```

Create a health check indicator

```ts
import { Injectable } from '@nestjs/common'
import {
    HealthIndicator,
    HealthIndicatorResult,
} from '@shelfjs/health-checks'

import { SamplePrismaService } from '../sample-services/sample-prisma.service'

@Injectable()
export class SamplePrismaConnectionHealthIndicator {
    constructor(private readonly prisma: SamplePrismaService) {}

    @HealthIndicator('sample-database')
    async isHealthy(): Promise<HealthIndicatorResult> {
        try {
            await this.prisma.$queryRaw<{ dt: string }[]>`SELECT now() dt`

            return {
                status: 'up',
            }
        } catch (error) {
            return {
                status: 'down',
                error: error.message,
            }
        }
    }
}
```

Then catch connection error of your ORM or transport service. As example I use Prisma client

```ts
async onModuleInit(): Promise<void> {
    try {
        // connect to the database
        await this.$connect()
    } catch (err) {
        // do not throw error here
        this.logger.error(err, err.stack)
    }
}
```

As a result we have



```json
{
  "ratio": 1,
  "uptime": 5,
  "timestamp": 1675597500626,
  "services": [
    {
      "name": "sample-database",
      "status": "up",
    },
    {
      "name": "my-service",
      "status": "up",
      "details": {
        "entitiesCreated": 500
      }
    }
  ]
}
```
npm package: @shelfjs/schematics
Description: Library contains utils to generate and execute commands working with Nx
Latest version: 1.6.3

# Schematics

Library contains utils to generate and execute commands working with Nx

```
npm i --save-dev @shelfjs/schematics
```

## Executors

### Prisma

Run prisma under your project configuration

Supports

- Generate
- Migrate deploy
- Migrate dev
- Migrate reset
- Pull
- Studio

Usage in `project.json`

```
{
  "name": "server",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "sourceRoot": "packages/server/src",
  "targets": {
    "generate": {
      "executor": "@shelfjs/schematics:prisma-generate",
      "outputs": ["{workspaceRoot}/node_modules/generatedprisma"], // for cache
      "options": {
        "schema": "{projectRoot}/prisma/schema.prisma" // provide if your schema not in {projectRoot}/src/prisma/schema.prisma
      }
    },
  }
}
```

## Generators

### Nest Module

Generate nest dynamic module with `.forRoot()` and module configs

Usage:

`--events` generate additional events provider interface. default: true

`--repository` generate additional repostiory provider interface. default: false

```bash
nx g @shelfjs/schematics:nest-module <module-name> <path from root>
```

### Nest CQRS

Generate nest command and queries with additional GraphQL/REST controllers

Usage:

`--graphql` generate GraphQL resolver

`--rest` generate REST controller

`--test` generate Jest tests

`--zod` generate ZOD validation

```bash
nx g @shelfjs/schematics:nest-cqrs <command/query> <name> <path from root>
```

### Nest features

Generate nest feature with additional GraphQL/REST controllers (from @shelfjs/features)

Usage:

`--graphql` generate GraphQL resolver

`--rest` generate REST controller

`--test` generate Jest tests

`--zod` generate ZOD validation

```bash
nx g @shelfjs/schematics:nest-feature <command/query> <name> <path from root>
```
npm package: @shelfjs/trpc
Description: Forked from: https://github.com/KevinEdry/nestjs-trpc/tree/main Version 1.6.1
Latest version: 1.0.0

# TRPC (NestJS)

Forked from: https://github.com/KevinEdry/nestjs-trpc/tree/main
Version 1.6.1

Changes:
- ConsoleLogger to Logger to support custom loggers
- Remove onModuleInit from GeneratorModule to be able to generate types out of app running
npm package: @sheliang/v-ui
Description: vue3, vite, element-plus, v-ui
Author: sheliang
Latest version: 0.0.12

# v-ui

此组件库基于 <b>Element Plus</b> (后续简称 element)，针对团队的开发风格和业务场景进行二次封装，这里统一声明兼容 element 所有的属性及事件（以 on 事件名绑定）;其实也仅是Vue + Element 的一种使用方式。

test git push