open-index/open-npm huggingface dataset:
npm package: @plicity/create
Description: npm init package for build pipelines in OpenShift with Gitlab
Author: Philipp Renoth
Latest version: 1.0.0-alpha.4

# PLICITY - `create` package

Package for `npm init @plicity ...` of the PLICITY Operator.

Refer to the [GitHub](https://github.com/plicity/plicity) or [NPM](https://www.npmjs.com/package/plicity) PLICITY documentation if you want to read more.
npm package: @plicity/operator
Description: Create your own build pipeline in OpenShift with Gitlab
Author: Philipp Renoth
Latest version: 1.0.0-alpha.8

# PLICITY - `operator` package

The PLICITY Operator implementation currently for OpenShit with Gitlab.

Refer to the [GitHub](https://github.com/plicity/plicity) or [NPM](https://www.npmjs.com/package/plicity) PLICITY documentation if you want to read more.
npm package: @plicity/operator-ui
Description: PLICITY operator UI
Author: Philipp Renoth
Latest version: 1.0.0-alpha.6

# PLICITY - `operator-ui` package

UI component of the PLICITY Operator for internal use.

Refer to the [GitHub](https://github.com/plicity/plicity) or [NPM](https://www.npmjs.com/package/plicity) PLICITY documentation if you want to read more.
npm package: @plinio_mayer/e-mailer
Description: A little script for development of email templates.
Author: PlinioMayer
Latest version: 1.2.2

# Intro
This is a simple script to help developing email templates. It is basically an easy to use abstraction of nodemailer. It currently supports sending html with embedded images.

# Instalation
Install it using:<br/>
`npm install -g @plinio_mayer/e-mailer`<br/>
or<br/>
`npm install @plinio_mayer/e-mailer`

# Usage

## Configuring
You need to make some initial configurations to use this script. Run the command below:<br/>
`e-mailer --init`<br/>
It'll prompt some questions about the host configurations. If you need to change them later you may repeat the command, or change the `config.json` in the root of the project manually.

## Send the email
After setting the environment variables you'll need an html file. Run the code below to use it:<br/>
```e-mailer --from < sender-email > --to < receiver-email > --sub < email-subject > < your-html-file-path >```<br/>
\*\*\***Use quotes if you need to send a subject with spaces**<br/>
\*\*\***Don't use backslash (\\) for html file path, use always slashes (/)**
<br/>

Example:<br/>
```e-mailer --from my.email@gmail.com --to his.email@gmail.com --sub "The best subject" my_folder/index.html```

## Images
e-mailer will automatically link the images in the imgs tags's srcs. You just need to make sure the html can be opened in the browser and the images are shown correctly.

## Known bugs
The currently package to read the console (readline-sync) allows to mask the password, but it cancels any input like backspace or ctrl+c. Unfortunately you'll have to close the terminal if misspell your password or want to terminate de process.

# Feedback
E-mail me: pctmayer@gmail.com
npm package: @pliny/cli
Description: Pliny CLI
Author: Timothy Lin
Latest version: 0.0.6

# `cli`

Command-line utility for initializing a new pliny app, code generation, content management, and other functions. It is meant to be user-friendly and easy to extend.

## Installation

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

## CLI Usage

Here are some examples of common commands:

### Create a new starter blog project called "my-blog"

```bash
pliny new --template=starter-blog my-blog
```

### Adding a blog page to an existing Next.js application:

```bash
pliny install add-blog ContentDir=data ContentName=Blog
```

### Add the blog-classic templates to the `layouts` folder:

```bash
pliny install add-classic
```

## Generator

Templating and code generation is supported with a modified version of `@blitzjs/generator`. In the `generators` directory you'll find the base `generator` class and other files that extend it. The subclasses aren't terribly interesting, most of the fun happens in the abstract parent class.

Recipes are passed through the generator and transformed accordingly. This relies on a custom templating language. Each variable in a recipe template surrounded by `__` (e.g. `__modelName__`) will be replaced with the corresponding value in the object returned from `Generator::getTemplateValues`. This type of replacement works in filenames as well. This allows CLI inputs to replace placeholder variables. For an example, see `recipes/add-blog`.

The generator framework also supports conditional code generation, similar to other common templating languages like handlebars. All model variables are exposed via `process.env` and can be used in conditional statements. The generator will not evaluate any expressions in the conditional, so the condition must be evaluated in the generator class and passed as a variable to the template. Both `if else` and ternary statements are supported, and for `if` statements no `else` is required:

```js
// VALID
if (process.env.someCondition) {
  console.log('condition was true')
}

// VALID
if (process.env.someCondition) {
  console.log('condition was true')
} else {
  console.log('condition was false')
}

// VALID
const action = process.env.someCondition
  ? () => console.log('condition was true')
  : () => console.log('condition was false')

// **NOT** VALID
// This will compile fine, but will not product the expected results.
// The template argument `someValue` will be evaluated for truthiness
// and the conditional will be evaluated based on that, regardless of
// the rest of the expression
if (process.env.someValue === 'some test') {
  console.log('dynamic condition')
}
```

## Credits

Much credit goes to [Blitzjs](https://github.com/blitz-js/blitz) of which this code is adapted from.

CLI is adapted from @blitzjs/cli, templating and generator adapted from @blitzjs/generator.
npm package: @pliny/installer
Description: Package installation for the Pliny CLI
Author: Timothy Lin
Latest version: 0.0.6

# `installer`

The installer package houses all of the types, classes, and utilities for building a Pliny Recipe. A Pliny recipe is effectively just a list of steps, represented as an array of objects that conform to one of the types in the `Executor` union type (`NewFileExecutor | AddDependencyExecutor | FileTransformExecutor`). These executors are processed by the framework, executed interactively by the user, and ultimately run to install new packages to an existing Pliny app.

You can find the implementation of all Executors in the `executors/` directory, stock transforms that we'll be supplying to authors in `transforms/`, and various utilities in `utils/`, including a `paths` utility that the user can access for common paths to modify such as `_document.tsx`.

## Credits

Adapted from [Blitz.js installer](https://github.com/blitz-js/blitz)
npm package: @plipag/ceci-ui
Description: PliPag's implementation of @mui/material
Author: Vinicius Borges
Latest version: 1.6.1

# ceci-ui

> A highly opinionated implementation of Material-UI.

[![NPM](https://img.shields.io/npm/v/@plipag/ceci-ui.svg)](https://www.npmjs.com/package/@plipag/ceci-ui) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Example

See a [live demo](https://musing-leakey-984ecc.netlify.app/).

## Install

```bash
# npm
npm install --save @plipag/ceci-ui

# yarn
yarn add @plipag/ceci-ui
```

## Usage

See below an example of using `Button` component.

```tsx
import React, { Component } from "react";

import { Button } from "ceci-ui";

class Example extends Component {
  render() {
    return <Button>Button Label</Button>;
  }
}
```

## Documentation

You can see our [stories here](https://youthful-brahmagupta-ae9527.netlify.app/).
Real documentation is coming soon.

## Testing

At this point, testing is not a priority. TypeScript provides us with the necessary stability for now.

## License

MIT © [plipag](https://github.com/plipag)
npm package: @plisio/api-client
Description: Plisio API nodejs library
Author: plisio
Latest version: 1.0.1

## Plisio NodeJs API library

To start using cryptocurrencies on your site you need to create an account on <https://plisio.net> and approve your domain under API setting page to get a **secret key**.

This secret key will be used for creating instance of the PlisioClient.

### Installation

**Composer**

You can install library via [npm](https://www.npmjs.com/) or [yarm](https://yarnpkg.com/) package manages. 

Run the following command in your terminal:

```bash
npm install @plisio/api-client
```