open-index/open-npm huggingface dataset:
npm package: @sharmaji_ag/ui-lib
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.0.11.
Latest version: 0.0.3

# UiLib

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.0.11.

## Code scaffolding

Run `ng generate component component-name --project ui-lib` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project ui-lib`.
> Note: Don't forget to add `--project ui-lib` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build ui-lib` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build ui-lib`, go to the dist folder `cd dist/ui-lib` and run `npm publish`.

## Running unit tests

Run `ng test ui-lib` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @sharmapukar217/dotenv-utils
Description: env utils to manage .env files
Author: Pukar Sharma
Latest version: 1.0.0

# dotenv-utils

`dotenv-utils` is a simple and interactive CLI utility to help you manage your `.env` files.  
It enables you to generate `.env.example` files by extracting keys from existing `.env` files, and also to create `.env` files interactively by filling in missing values based on `.env.example`.

---

## Features

- Generate `.env.example` files by copying keys from your `.env` and stripping out the values to avoid leaking secrets.  
- Create or update your `.env` file interactively by prompting for each variable defined in `.env.example`.  
- Skip variables during configuration by pressing `Ctrl+C`.  
- Clear informative messages and error handling for better developer experience.

---

## Installation

You can install `dotenv-utils` globally via npm:

```bash
npm install -g dotenv-utils
```

Or use it directly via `npx` without global install:

```bash
npx dotenv-utils <command> [options]
```

---

## Commands

### `gen-env-example`

Generate a `.env.example` file by copying all keys from your `.env` file, replacing all values with empty strings.

```bash
dotenv-utils gen-env-example -i .env -o .env.example
```

#### Options

- `-i, --input <file>`: Path to the source `.env` file (default: `.env`)  
- `-o, --output <file>`: Path where the generated `.env.example` file will be saved (default: `.env.example`)

---

### `configure-env`

Create or update your `.env` file interactively by reading keys from a `.env.example` file and prompting you to enter their values.

```bash
dotenv-utils configure-env -i .env.example -o .env
```

#### Options

- `-i, --input <file>`: Path to the `.env.example` file to read keys from (default: `.env.example`)  
- `-o, --output <file>`: Path where the resulting `.env` file will be saved (default: `.env`)

You will be prompted to enter a value for each environment variable defined in `.env.example`. If you want to skip a variable, press `Ctrl+C` to abort the process.

---

## Usage Example

1. Generate an example file from your existing `.env`:

```bash
dotenv-utils gen-env-example
```

2. Commit `.env.example` to your repository to share environment variable keys without secrets.

3. When setting up a new environment, run:

```bash
dotenv-utils configure-env
```

and fill in the requested values interactively.

---

## Development

### Build

Install dependencies, then run:

```bash
npm run build
```

### Run locally

Run your CLI directly from the built files:

```bash
node dist/index.js <command> [options]
```

---