open-index/open-npm huggingface dataset:
npm package: @quarva/netlify-plugin-sitrep
Description: A Netlify build plugin that injects build and deploy information into the DOM for debugging.
Author: Quarva
Latest version: 0.0.8

# netlify-plugin-sitrep

[![Netlify Status](https://api.netlify.com/api/v1/badges/ed60732d-7271-432e-aada-70397b8f8ccf/deploy-status)](https://app.netlify.com/sites/netlify-build-sitrep/deploys) ![npm (scoped)](https://img.shields.io/npm/v/@quarva/netlify-plugin-sitrep) [![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2FQuarva%2Fnetlify-plugin-sitrep.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2FQuarva%2Fnetlify-plugin-sitrep?ref=badge_shield)

A Netlify build plugin that injects build and deploy information into the DOM for debugging.

[Live demo](https://netlify-build-sitrep.netlify.app)

![Demo](https://github.com/Quarva/quarva.github.io/blob/master/img/netlify-build-sitrep/demo.gif?raw=true)

## Usage

### Set up your Netlify environment variables

The plugin accesses Netlify's postprocessing snippet injection using the Netlify API, so we need to provide an access token.

1. Sign in to Netlify and navigate to User Settings → [Applications](https://app.netlify.com/user/applications)
2. Generate a new personal access token
3. Store that personal access token as a [build environment variable](https://docs.netlify.com/configure-builds/environment-variables) called `BUILD_SITREP_TOKEN` in the site(s) you want to use the plugin with.

### Required environment variables for development

| Variable Name |Description |
|--- | --- |
|BUILD_SITREP_TOKEN|Must be configured by the user|
|SITE_ID|Must be configured by the user|
|DEPLOY_ID|provided by Netlify, but can be configured by the user|
|BUILD_ID|provided by Netlify, but can be configured by the user|

### Install

```bash
npm install --save @quarva/netlify-plugin-sitrep

or 

yarn add @quarva/netlify-plugin-sitrep
```

### Add the plugin to `netlify.toml`

```toml
[[plugins]]
package = "@quarva/netlify-plugin-sitrep"
```

Note: The `[[plugins]]` line is required for each plugin, even if you have other plugins in your `netlify.toml` file already.

### Configuration

By default, the plugin won't inject any data in a production context. You can adjust that with the `allow_prod` input.

```toml 
[[plugins]]
package = "@quarva/netlify-plugin-sitrep"
  [plugins.inputs]  
    "allow_prod" = ""
    # If true, the plugin will inject data even when run in a production context.
    "verbose" = ""
    # If true, the plugin will write each step to the deploy log.
```
npm package: @quasar-ai/lolth.tools.publisher
Description: Static website publish tools
Author: 0x1C
Latest version: 0.1.1

# lolth.tools.publisher

A toolset for publishing static website, companied with project `lolth.server.static`

It is currently for:

- Convert HTML files into handlebars templates with `{{ .BaseURL }}` placeholders for any relative path
- Publish asset files to S3 storage

## Install

Install with yarn 

``` bash
yarn -D lolth.tools.publisher
```

or npm

``` bash
npm install -D lolth.tools.publisher
```

## Make Templates

``` bash
lopath tpl [ROOT_DIR] [-d|--dryrun]
```

Scan HTML files recursively in `ROOT_DIR` and make templates. Note that if `ROOT_DIR` is not specified, folder *dist* will be used as default.

**HTML files will be overridden by this command.**

You can run this command with flag `-d` or `--dryrun` to test if there's any error and for checking if all relative paths are detected.

## Publish To Server

##### To AWS S3

> For now this is the only service supported. More services may be added on need.

``` bash
lopath pub s3 <BUCKET> [ROOT_DIR] [-d|--dryrun]
```

Sync and push files in `ROOT_DIR` to an AWS S3 bucket. Note that if `ROOT_DIR` is not specified, folder *dist* will be used as default.

`BUCKET` refers to an S3 bucket identifier, which must starts with `s3://`. Take `s3://foo-bucket` as an example.

You can run this command with flag `-d` or `--dryrun` to check files to be synchronized before actually pushing them.
npm package: @quasar-army/quasar-app-extension-blue
Description: Simple VueModel integration with Quasar Framework
Author: luke@ldiebold.com
Latest version: 0.0.12

# Quasar App Extension quasar-ui-firebase

> Add a short description of your App Extension. What does it do? How is it beneficial? Why would someone want to use it?

[![npm](https://img.shields.io/npm/v/quasar-app-extension-firebase.svg?label=quasar-app-extension-firebase)](https://www.npmjs.com/package/quasar-app-extension-firebase)
[![npm](https://img.shields.io/npm/dt/quasar-app-extension-firebase.svg)](https://www.npmjs.com/package/quasar-app-extension-firebase)

# Install
```bash
quasar ext add quasar-ui-firebase
```
Quasar CLI will retrieve it from NPM and install the extension.

## Prompts

> If your app extension uses prompts, explain them here, otherwise remove this section and remove prompts.js file.

# Uninstall
```bash
quasar ext remove quasar-ui-firebase
```

# Info
> Add longer information here that will help the user of your app extension.

# Other Info
> Add other information that's not as important to know

# Donate
If you appreciate the work that went into this App Extension, please consider [donating to Quasar](https://donate.quasar.dev).

# License
MIT (c) luke@ldiebold.com