open-index/open-npm huggingface dataset:
npm package: @penfold/github-actions-include
Description: > Simple but effective partials system for GitHub Actions
Author: Penfold
Latest version: 1.0.1

# github-actions-include

> Simple but effective partials system for GitHub Actions

## What it does

Compiles GitHub Actions workflows with "partials", ie. partial workflow YAML
configuration, using an `#!include(partial_name)` directive.

## Example

Workflow:

```yaml
# github/workflows/cleanup.yml
name: Cleanup
on: [push]
jobs:
  #!include(setup_environment)
```

Partial:

```yaml
# github/partials/setup_environment.yml
setup_env:
    name: Setup environment
    runs-on: ubuntu-latest
    steps: 
        # ...
```

Result:

```yaml
# .github/workflows/cleanup.yml
name: Cleanup
on: [push]
jobs:
  setup_env:
    name: Setup environment
    runs-on: ubuntu-latest
    steps: 
        # ...
```


## Requirements

- Husky: https://github.com/typicode/husky

## Install

NPM:

```
npm install --dev @penfold/github-actions-include
```

Yarn:

```
yarn add --dev @penfold/github-actions-include
```

## CLI Usage

```
$ github-actions-include --help
Options:
  --help                  Show help                                    [boolean]
  --version               Show version number                          [boolean]
  --partialsDir           Path to partials                              [string]
  --workflowsDir          Path to workflows (must not be .github/workflows)
                                                             [string] [required]
  --includeWarningReadme  Include warning README.md in .github/workflows
                                                       [boolean] [default: true]
```

## API Usage

```
const githubActionsInclude = require("github-actions-include");

// Options object and all fields are optional
githubActionsInclude({
  workflowsDir: "github/workflows",
  partialsDir: "github/partials",
  includeWarningReadme: true,
});
```

## Options

### `workflowsDir`

Default: `github/workflows`

The folder in your project where you will write your GH Actions workflows.

Cannot be `.github/workflows`.

### `partialsDir`

Default: `github/partials`

The folder in your project where you will write your GH Actions partials.

### `includeWarningReadme`

Default: `true`

Whether to include a warning README in `.github/workflows` that tells developers not to make
changes in that folder, but in the folder specified by `workflowsDir`.

## License

Create by [Penfold](https://getpenfold.com) and released under the MIT license.
npm package: @penfold/validate-env-vars-webpack-plugin
Description: > A webpack plugin to validate usage of environment variables
Author: Sam Gluck
Latest version: 1.1.0

# validate-env-vars-webpack-plugin

> A webpack plugin to validate usage of environment variables

## Webpack version support

This plugin has only been tested with webpack >= 5.6.0.

## Options

### `knownEnvVars`

- type: _see the sections below for supported values_
- default: `Object.keys(process.env)`

Defines the list of known environment variables.

The plugin will produce an error for any environment variable used that is not in this list.

The field supports different sources for the list of env vars.

#### Array

Validate against a list of environment variables.

Example:

```javascript
knownEnvVars: ["PROJECT_NAME", "SECRET"]
```

#### AWS SecretsManager

Validate environment variables against a secret in AWS SecretsManager. 

The secret should be a key/value secret rather than plain text.

Give `knownEnvVars` an object with the properties:

- `secretId` (required) - the name of the secret in SecretsManager
- `accessKeyId` (required)
- `secretAccessKey` (required)
- `region` (required)
- `sessionToken` (optional)
- `secretVersionId` (optional)
- `secretVersionStage` (optional)

Example:

```javascript
knownEnvVars: {
    secretId: "api-env-vars",
    accessKeyId: process.env.AWS_ACCESS_KEY_ID,
    secretAccessKey: process.env.AWS_SECRET_ACCESS_KEY,
    region: "eu-west-1"
}
```

#### .env file

Validate environment variables against an .env file.

Give `knownEnvVars` a string file path to the .env file.

For example:

```javascript
knownEnvVars: path.resolve(__dirname, "../.env")
```

### `includePaths`

- type: `[String|RegExp]`
- default: `[]`

Defines the file paths to include in the validation.

```javascript
includePaths: [path.resolve(__dirname, "src")]
```

### `excludePaths`

- type: `[String|RegExp]`
- default: `[]`

Defines the file paths to ignore in the validation.

Example:

```javascript
excludePaths: [path.resolve(__dirname, "src/generated")]
```

### `ignoreEnvVars`

- type: `String[]`
- default: `[]`

A list of environment variable names to exclude from the validation.

Example:

```javascript
ignoreEnvVars: ["RUNTIME_VALUE"]
```

### `knownEnvVarsTimeout`

- type: `Number`
- default: `5000`

When using an external source (eg. AWS SecretsManager) for `knownEnvVars`, this defines the amount of time in milliseconds
to wait for the list of environment variables to be resolved before exiting with an error.

Example:

```javascript
knownEnvVarsTimeout: 2000 // 2 seconds
```

## Usage

Add the plugin to your webpack plugins array. For example:

```javascript
plugins: [
    new ValidateEnvVarsPlugin({
        knownEnvVars: ["PROJECT_NAME", "SECRET"],
        includePaths: [path.resolve(__dirname, "src")]
    })
]
```

## Example error

```shell
ERROR in ./src/app/api.ts
Unrecognised environment variable: WEBSITE_URL
 @ ./src/setup.ts 27:15-35
 @ ./src/index.ts 15:33-55
```

## Author & License

`validate-env-vars-webpack-plugin` was created by [Penfold](https://getpenfold.com) and is released under the MIT license.
npm package: @penfoldium/lyrics-search
Description: A package to search for song lyrics on Genius
Author: Penfoldium
Latest version: 2.0.3

# 🔍 lyrics-search

## 🤔 How does it work?
We use the [Genius API](https://genius.com/developers) for the actual search and then we scrape the lyrics from the Genius page of the song, because their API does not return the lyrics.

## 📝 Requirements
- [Node.js](https://nodejs.org/en/)
- NPM (comes with Node.js)

## 💿 Installation
`npm install @penfoldium/lyrics-search`

## 🖊 Usage example
```js
const lyrics_search = require('@penfoldium/lyrics-search');

const Lyrics = new lyrics_search('Genius Access Token');

const sickoMode = `She's in love with who I am
Back in high school, I used to bus it to the dance (Yeah)`; // Because we used backticks we can have new lines between the strings!

Lyrics.search(sickoMode)
    .then(console.log) // Short for .then(result => console.log(result))
    .catch(console.error) // Short for .catch(error => console.error(error))
```
npm package: @peng-oss/expo-aliyun-oss
Description: expo package for alioss sdk
Author: peng-oss
Latest version: 0.1.1

# expo-aliyun-oss

expo package for alioss sdk

# API documentation

- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/aliyun-oss/)
- [Documentation for the main branch](https://docs.expo.dev/versions/unversioned/sdk/aliyun-oss/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/archive/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install expo-aliyun-oss
```

### Configure for Android




### Configure for iOS

Run `npx pod-install` after installing the npm package.

# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).