open-index/open-npm huggingface dataset:
npm package: @pushpalatha_h/test-package
Description: This project demonstrates how to build a monorepo of dependent components that are installed as a single package. It builds a library of components similar to Angular Material.
Latest version: 0.0.2

# Dmv

This project demonstrates how to build a monorepo of dependent components that are installed as a single package. It builds a library of components similar to Angular Material.

Most of the `nx` commands work as expected with the exception of those that are dependent the `dep-graph`. Commands that use `affected` don't work either.

# Building The Library

To build the component library for distribution run

`npm run build-libs`

This triggers a sequence of build scripts in the `package.json` to build the components in their order of dependencies.

# Consuming The Library

This library builds the set of components that are installed using a form like

`npm install @namespace/library`

This installs the collection of components in the project.

Angular Material supports 2 styles of importing into applications:

```
import { CoreModule } from '@dmv/demo'`
import { CoreModule } from '@dmv/demo/core'
```

This repo supports the latter style only.

# Project Structure and Building

In `nx` parlance, a *library* is a unit of dependency and build which can include one or more angular *components*.

In this instance, we treat and think of the `nx` library as a component.

Building the component for distribution is a matter of configuring the `ng-packagr` control files.

## Configure Component `ng-package.json`

Define the destination based on the desired distribution package structure:

```
  "dest": "../../dist/@dmv/demo/button",
```

The `umdId` provides the id for the module. The map of `umdModuleIds` keeps the complier from guessing about the dependencies:

```
    "umdId": "dmv.button",
    "umdModuleIds": {
      "@dmv/demo/core": "dmv.core",
      "@dmv/demo/link": "dmv.link"
    }
```

## Configure Component `package.json`

The main thing to configure here is the component name including the npmjs namespace:

```
  "name": "@dmv/demo/button",
```

## Configure Component `tsconfig.lib.json`

When a component is built it reads the source for the component from the `src/libs` path. The dependencies for the component must be resolved from the previously built components. To enable this we need to add the path to the compiler options:

```
  "compilerOptions": {
    ...
    "paths": {
      "@dmv/*": ["dist/@dmv/*"]
    }
  },
```

## Configure Repo `tsconfig.json`

In order for Visual Studio Code to resolve the dependencies we need to configure the components in the project level `tsconfig.json`

```
  "compilerOptions": {
    ...
    "paths": {
      "@dmv/demo/core": ["libs/core/src/index.ts"],
      "@dmv/demo/button": ["libs/button/src/index.ts"],
      "@dmv/demo/link": ["libs/link/src/index.ts"]
    }
  },
```
npm package: @pushpalsdev/cli
Description: PushPals terminal CLI for LocalBuddy -> RemoteBuddy orchestration
Latest version: 1.0.39

# @pushpalsdev/cli

Terminal-first PushPals client that routes chat through `LocalBuddy -> RemoteBuddy`.

## Install

```bash
npm i -g @pushpalsdev/cli
```

or:

```bash
bun install -g @pushpalsdev/cli
```

## Run

From a git repository that is attached to your running PushPals stack:

```bash
pushpals
```

The CLI hard-fails if:

- current directory is not a git repository
- LocalBuddy is attached to a different repo root
- Bun runtime is not installed (for npm-installed entrypoint execution)

Behavior:

- If LocalBuddy is unavailable, CLI auto-start bootstraps embedded
  `server + localbuddy + remotebuddy + source_control_manager`.
- Auto-start does not clone the PushPals repo; it downloads release-tagged runtime binaries
  and prompt/config assets into `~/.pushpals/runtime`.
- Override runtime tag with `pushpals --runtime-tag vX.Y.Z`.
- Disable auto-start with `pushpals --no-auto-start`.

## No npm/Bun install

Download native binaries from GitHub Releases:

https://github.com/PushPalsDev/pushpals/releases
npm package: @pushpendersingh/rn-barcode
Description: For the react native framework, there is a barcode scanner component.
Author: Pushpender Singh
Latest version: 1.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.


# 🚧 🚧 🚧
## @pushpendersingh/rn-barcode is deprecated.

The @pushpendersingh/rn-barcode package is designed specifically for Android devices and provides reliable barcode scanning functionality and new [@pushpendersingh/react-native-scanner](https://github.com/pushpender-singh-ap/react-native-scanner) package, which supports the latest Fabric Native architecture for both Android and iOS platforms. This cutting-edge package offers even more advanced features and improved performance, making it the perfect choice for developers who want to deliver fast and accurate scanning capabilities to their users.

@pushpendersingh/rn-barcode is now deprecated in favor of [@pushpendersingh/react-native-scanner](https://github.com/pushpender-singh-ap/react-native-scanner).

<br />
<br />

> You can find the old code of @pushpendersingh/rn-barcode [here](https://github.com/pushpender-singh-ap/rn-barcode/tree/master).