open-index/open-npm huggingface dataset:
npm package: @barneycarroll/life-cycle
Description: A no-op custom element which exposes lifecycle hooks to consuming view frameworks
Author: Barney Carroll
Latest version: 1.0.0-rc.1

# `<life-cycle/>`

`<life-cycle/>` is a [custom element](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements) for framework-agnostic lifecycle hooks. 

## What?

The various view frameworks of the world have different APIs of exposing the underlying DOM nodes & fundamental entity lifecycle (create, update, destroy) - some don't expose any at all. `<life-cycle/>` forwards each of the DOM [lifecycle callbacks](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements#using_the_lifecycle_callbacks_) to corresponding property methods declared on instantiation, allowing CRUD directives and access to local DOM objects. Meanwhile, it applies a style of `display:contents` so as not to affect rendering. 

## How?

Each lifecycle method on the custom element prototype will call corresponding properties on any `<life-cycle/>` index, with the same signature:

| Custom element method | `<life-cycle>` property   
|-|-
|`connectedCallback`        |`connected`       
|`disconnectedCallback`     |`disconnected`    
|`adoptedCallback`          |`adopted`         
|`attributeChangedCallback` |`attributeChanged`

Because `attributeChanged` requires that observed attributes be determined ahead of time, we reserve an attribute called simply `attribute` to trigger its execution.

## Why?

As an example, [Hyperapp](https://github.com/jorgebucaran/hyperapp) - a minimal virtual DOM library with a strong remit on functional purity - doesn't expose any API for interfacing with generated DOM; meanwhile, an application written with [`seview`](https://github.com/foxdonut/seview#seview-s-expression-view) would want to avoid library-specific APIs as far as possible in order to allow the same application view code to run with interchangeable rendering engines. With the `<life-cycle/>` element, either - or both - of these can be used in a way that allows setup & teardown logic per node, conditional updates, and DOM node exposure.
npm package: @bart.sk-ecommerce/react-eshop-redirects
Description: Handler for redirects in bart.sk ecommerce
Author: Laci Perduk
Latest version: 1.0.11

# React eshop redirects

Implementation of admin redirects to REACT frontend. 

## Usage

**general reducer**

```typescript
    case REDIRECT: {
      return redirectReducer(state, payload);
    }
```

**init of APP**
```typescript
    await dispatch(checksRedirect(props.location));
```

### API

For Api docs looks at: [Docs API](docs/README.md)
npm package: @barusu/util-cli
Description: utils for creating node.js command line program
Author: guanghechen
Latest version: 0.2.1
Deprecated: Please use @guanghechen/commander-helper instead

<header>
  <h1 align="center">
    <a href="https://github.com/guanghechen/barusu/tree/main/utils/cli#readme">@barusu/util-cli</a>
  </h1>
  <div align="center">
    <a href="https://www.npmjs.com/package/@barusu/util-cli">
      <img
        alt="Npm Version"
        src="https://img.shields.io/npm/v/@barusu/util-cli.svg"
      />
    </a>
    <a href="https://www.npmjs.com/package/@barusu/util-cli">
      <img
        alt="Npm Download"
        src="https://img.shields.io/npm/dm/@barusu/util-cli.svg"
      />
    </a>
    <a href="https://www.npmjs.com/package/@barusu/util-cli">
      <img
        alt="Npm License"
        src="https://img.shields.io/npm/l/@barusu/util-cli.svg"
      />
    </a>
    <a href="https://github.com/nodejs/node">
      <img
        alt="Node.js Version"
        src="https://img.shields.io/node/v/@barusu/util-cli"
      />
    </a>
    <a href="https://github.com/tj/commander.js/">
      <img
        alt="Commander version"
        src="https://img.shields.io/npm/dependency-version/@barusu/util-cli/peer/commander"
      />
    </a>
    <a href="https://github.com/prettier/prettier">
      <img
        alt="Code Style: prettier"
        src="https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square"
      />
    </a>
  </div>
</header>
<br/>


## Install

* npm

  ```bash
  npm install --save @barusu/util-cli
  ```

* yarn

  ```bash
  yarn add @barusu/util-cli
  ```

## Usage


[homepage]: https://github.com/guanghechen/barusu/tree/main/utils/cli#readme
npm package: @base-cms/marko-web-reveal-ad
Description: Custom Reveal Ad Marko/Vue components for BaseCMS websites
Author: Jacob Bare
Latest version: 1.37.0

# BaseCMS Marko Web Reveal Ad Components

## Installation
1. Add `@base-cms/marko-web-revel-ad` to your project/site.

2. Include the Browser plugin.
  ```js
  // your-site/browser/index.js
  import RevealAd from '@base-cms/marko-web-reveal-ad/browser';

  RevealAd(Browser);

  export default Browser;
  ```

3. Include the styles
  ```scss
  // your-site/server/styles/index.scss
  @import "../../node_modules/@base-cms/marko-web-reveal-ad/scss/reveal-ad";
  ```

4. Load the listener component on all pages, as close to the opening `<body>` tag as possible. This is usually handled in a common site `document.marko` component
  ```marko
  <marko-web-document ...input>
    <@head>
      <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
      <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
      <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
      <link rel="manifest" href="/site.webmanifest">
      <marko-web-gam-init />
      <${input.head} />
      <marko-web-gam-enable />
      <marko-web-gam-targeting key-values={ uri: req.path } />
    </@head>
    <@above-container>
      <marko-web-reveal-ad-listener />
      <default-theme-site-header />
      <default-theme-site-menu />
      <${input.aboveContainer} />
    </@above-container>
  </marko-web-document>
  ```