open-index/open-npm huggingface dataset:
npm package: @piducancore/fonts-andale-mono
Description: Andalé Mono font-face generated using Transfonter.
Latest version: 1.0.1

# fonts-andale-mono

[**Andalé Mono**](https://docs.microsoft.com/es-es/typography/font-list/fonts-andale-mono) _@font-face_ generated using [Transfonter](https://transfonter.org).

![characters demo](https://docs.microsoft.com/es-es/typography/font-list/images/andalemono1.png)

## Install

```bash
yarn add @piducancore/fonts-andale-mono
```

## Usage

Import the font somewhere in your project like this:

```js
import "@piducancore/fonts-andale-mono"
```

Then, use the font in your styles like this:

```css
font-family: "Andale Mono";
```

That's it.

## Preview

![](https://docs.microsoft.com/es-es/typography/font-list/images/andalemono2.png)
npm package: @piducancore/gatsby-source-cloudinary-metadata
Description: This plugin turns your Cloudinary media files including its embedded metadata into Gatsby nodes.
Author: @piducancore
Latest version: 1.0.3

# gatsby-source-cloudinary-metadata

This plugin turns your Cloudinary media files _including its embedded metadata_ into Gatsby nodes.

## Requirements

All you need is a [Cloudinary](https://www.cloudinary.com) account with some images, your `cloud_name`, `api_key` and `api_secret`.

## Usage

In your Gatsby project run to following to install:

```bash
yarn add @piducancore/gatsby-source-cloudinary-metadata
```

Then in your `gatsby-config.js` file, include the plugin like this:

```js
// gatsby-config.js
module.exports = {
  plugins: [
    // ...
    {
      resolve: `@piducancore/gatsby-source-cloudinary-metadata`,
      options: {
        cloud_name: "YOUR_CLOUD_NAME", // required
        api_key: "YOUR_API_KEY", // required
        api_secret: "YOUR_API_SECRET", // required
        max_results: 500, // optional, default: 10
        prefix: `uploads/`, // optional
        type: `upload`, // required if prefix param specified above, otherwise optional
      },
    },
  ],
}
```

That's it.

## Example

To see the newly created Gatsby nodes you can go to your site's GraphiQL (`http://localhost:8000/___graphql`) and try something like the following.

### Sample query

If we wanted to get all the nodes this plugin created (`allCloudinaryMedia`) sorted by the embedded metadata's creation date (`CreateDate`) we could do something like this:

```graphql
{
  allCloudinaryMedia(
    sort: { order: ASC, fields: image_metadata___CreateDate }
  ) {
    totalCount
    nodes {
      public_id
      image_metadata {
        CreateDate
      }
    }
  }
}
```

### Sample response

And we should get something like this:

```graphql
{
  "data": {
    "allCloudinaryMedia": {
      "totalCount": 2,
      "nodes": [
        {
          "public_id": "uploads/some_image",
          "image_metadata": {
            "CreateDate": "2019:10:19 20:21:28"
          }
        },
        {
          "public_id": "uploads/some_other",
          "image_metadata": {
            "CreateDate": "2019:10:20 16:10:44"
          }
        }
      ]
    }
  }
}
```

## Notes

The plugin makes a first query to the Cloudinary API to get your images based on the options provided at configuration. Then uses the images `public_id` values to query them again one by one, to get the `image_metadata` from each.

In theory, every optional parameter for the `resources` endpoint should work to query and/or filter your images for the _first query_ mentioned above.

You can check all optional parameters at the [Get resources](https://cloudinary.com/documentation/admin_api#get_resources) section of the Cloudinary API documentation.
npm package: @pie-api/mru
Description: mono repo utils - has strong opinions!
Latest version: 1.4.0

# mru

mono repo utils - has strong opinions!

You have a cloud funtion here: functions/my-fn, then `mru my-fn` will:

 1. bundles functions/my-fn/lib/index.ts
 2. creates zip file 
 3. pushes zip to gcloud storage
 4. gcloud deploys w/ env vars + flags

`mru my-container` will:

1. bundle containers/my-container/lib/index.ts
2. docker builds w/ tag
3. docker push tag
3. gcloud deploys w/ env vars


## mru.config.js

mru will read `mru.config.js` from the cwd. It can overrides the following properties.
mru will also read in command line flags, these will take highest priority.

From the above we build a `Config` that has the following form:

```ts
export type Config = {

  envDir: string; // required 
  projectId: string; // required 
  region: string; // required 
  bucketPath: (projectId: string, region: string) => string;  // required
  dockerRegistry: string; // 'grc.io'
  containers: string; //'containers'
  functions: string; //'functions'
  dryRun: boolean; // false
  /**
   * All true by default set --no-bundle to disable bundle. 
   * same for the others
   */
  steps: {
    bundle: boolean;
    docker: boolean;
    deploy: boolean;
  };
  /** 
   * This is generated by mru - don't need to set it
   */
  git?: {
    hash: string;
  };
}
```

## cloud config

mru will generate the deployment arguments for a container/function using 2 sources:

1. the loaded env file loaded from `$envDir/$projectId.yaml`.
1. the `cloud` map in the package's `package.json`

### Example
```json
{
  "name": "my-fn",
  "cloud": {
    "deployFlags": {
      "foo":  "$ENV_VAR"
    },
    "environment":{
      "ENV_VAR": "$ENV_VAR"
    }
  }
}
```
env: 
```yaml
ENV_VAR: bar

```
in the above:
1.  `deployFlags.foo` will be converted to `--foo bar` and passed to the appropriate gcloud command.
1. the env vars will be set to `--set-env-vars ENV_VAR=bar`

By doing this, we can put all our env vars in 1 place, and each pkg will only pull what it needs.