open-index/open-npm huggingface dataset:
npm package: @kb_lee/react-countdown-hook
Description: react countdown hook
Author: Kangbok Lee
Latest version: 0.1.2

# Welcome to react-countdown-hook!

A simple react hook to towndown seconds between two date object

## Demo
codeSandbox: Demo[https://codesandbox.io/s/usecountdown-kwygye]

## install
```
npm install --save @kb_lee/react-countdown-hook
```

## Example
```javascript
import useCountDown from "@kb_lee/react-countdown-hook";

export default function App() {
  // useCountDown(${secdons}, ${init_time});
  const { useCountDownValue } = useCountDown(10000, 0);

  return (
    <div className="App">
      <h1>Countdown to Zero</h1>
      <span>remain seconds: {useCountDownValue}</span>
    </div>
  );
}
```
npm package: @kba-tools/create-express-app
Description: Boilerplate for an Express App.
Author: Kerala Blockchain Academy
Latest version: 0.6.0

# Create Express App

A minimalist boilerplate generator for quickly setting up a new [Express](https://expressjs.com/) application — with your choice of language and an optional template engine.

## Features

- Supports **JavaScript** and **TypeScript**
- Optional support for **EJS** or **Handlebars**
- Automatically installs dependencies using your preferred package manager (`npm`, `pnpm`, or `yarn`)
- Generates a clean, minimal project structure

## Quick Start

Run the following command and follow the interactive prompts:

```bash
npx @kba-tools/create-express-app
```

You’ll be asked to choose:

- Language: JavaScript or TypeScript
- Template engine: None, EJS or Handlebars
- Package manager: npm, pnpm, or yarn

Once confirmed, the app scaffold will be generated and dependencies installed automatically.

```bash
cd my-express-app
npm start
```

## Example Structure

```
my-express-app/
├── src/
│   ├── routes/
│   ├── views/
│   └── app.js
├── package.json
└── README.md
```

## Why Use This?

Skip repetitive Express setup steps and start coding immediately.
**Create Express App** provides a clean, ready-to-use foundation for any Express project.

## License

Distributed under the **MIT License**.
See [`LICENSE`](./LICENSE.md) for details.
npm package: @kba-tools/touch-contract
Description: Creates boilerplate smart contracts in Solidity & Vyper.
Author: Kerala Blockchain Academy
Latest version: 4.0.0

# Touch Contract

**Touch Contract** is a command-line utility that generates boilerplate smart contracts in **Solidity** and **Vyper**, helping developers quickly scaffold common contract types for blockchain projects.

## Supported Contract Templates

1. **Storage** — Solidity & Vyper
2. **Certificate** — Solidity & Vyper
3. **Auction** — Vyper
4. **NFT** — Solidity
5. **Voting** — Vyper

## Quick Start

Run the following command to generate a new smart contract template:

```shell
npx @kba-tools/touch-contract
```

## License

This project is distributed under the **MIT License**.
npm package: @kba/anno-acl
Description: Anno authorization rules
Author: kba
Latest version: 0.0.1

# anno-acl
> Authorization for anno-stores

## ACL Users

* `role`: An optional global role of a user
* `id`: The user ID such as their homepage or email address
* `perm`: An array of objects of collection-specific roles
  * `collection`: The collection these roles apply to
  * `role`: The roles

## ACL Rules

Rules for authorization are expressed as
[sift-rule](https://github.com/kba/sift-rule) rules and read as JSON from the
environment variable `ANNO_ACL_RULES`.

Rules are an ordered list of `CONDITION`-`RESULT`-`DESCRIPTION` triplets:

* `CONDITION` is a sift query on an object encoding the request context
  * `method`: One of the methods of [anno-store](https://github.com/kba/anno/tree/master/anno-store)
  * `anno`: The existing annotation
    * See [data-model.yml in anno-schema](https://github.com/kba/anno/tree/master/anno-schema/data-model.yml)
  * `newAnno`: The new annotation (in case of `create`, `revise`)
  * `user`: The user calling the method, see [ACL Users](#acl-users)
  * `collection`: ID of the collection in question. Defaults to `default`
* `RESULT` is `true` to allow or `false` to deny the request
* `DESCRIPTION` is an optional description of the rule
npm package: @kba/anno-mw-acl-static
Description: Anno ACL middleware (static data)
Author: kba
Latest version: 0.0.1

# anno-mw-acl-static

> Authorization for anno-stores

## ACL Users

* `role`: An optional global role of a user
* `id`: The user ID such as their homepage or email address
* `perm`: An array of objects of collection-specific roles
  * `collection`: The collection these roles apply to
  * `role`: The roles

## ACL Rules

Rules for authorization are expressed as
[sift-rule](https://github.com/kba/sift-rule) rules and read as JSON from the
environment variable `ANNO_ACL_RULES`.

Rules are an ordered list of `CONDITION`-`RESULT`-`DESCRIPTION` triplets:

* `CONDITION` is a sift query on an object encoding the request context
  * `method`: One of the methods of [anno-store](https://github.com/kba/anno/tree/master/anno-store)
  * `anno`: The existing annotation
    * See [data-model.yml in anno-schema](https://github.com/kba/anno/tree/master/anno-schema/data-model.yml)
  * `newAnno`: The new annotation (in case of `create`, `revise`)
  * `user`: The user calling the method, see [ACL Users](#acl-users)
  * `collection`: ID of the collection in question. Defaults to `default`
* `RESULT` is `true` to allow or `false` to deny the request
* `DESCRIPTION` is an optional description of the rule
npm package: @kba/default-pager
Description: launch $PAGER in your program
Author: James Halliday
Latest version: 1.1.1

default-pager
======

Launch $PAGER in your program.

adapted from [substack/node-editor](https://github.com/substack/node-editor)

Example
-------

``` js
var pager = require('default-pager')

stream.pipe(pager(function () {
  //user exited
  console.log('done!')
})
```

API
---

### `pager([opts], [cb(code, signal)])`

Launches pager process and returns a writable stream. `cb(code, signal)` is fired once the pager is exited.

#### `opts.pager`

Type: `String` <br>
Default: `$PAGER` <br>

Pager program to launch.

#### `opts.args`

Type: `[String]` <br>
Default: `[]` <br>

Arguments passed to the pager program.

License
-------

MIT
npm package: @kba/find-parent-dir
Description: Finds the first parent directory that contains a given file or directory.
Author: Thorsten Lorenz
Latest version: 0.3.0

# find-parent-dir [![build status](https://secure.travis-ci.org/thlorenz/find-parent-dir.png)](http://travis-ci.org/thlorenz/find-parent-dir)

Finds the first parent directory that contains a given file or directory.

    npm install find-parent-dir

```js
// assuming this is called from a file in a subdirectory of /myprojects/foo which contains .git directory
var findParentDir = require('find-parent-dir');

findParentDir(__dirname, '.git', function (err, dir) {
  // has err if some file access error occurred
  console.log(dir); // => /myprojects/foo/
  
  // if parent dir wasn't found, dir is null
})

// Same using `sync` method
var dir;
try { 
  dir = findParentDir.sync(__dirname, '.git');
  console.log(dir); // => /myprojects/foo/
  // if parent dir wasn't found, dir is null
} catch(err) {
  console.error('error', err); 
}
```
npm package: @kba/vfs
Description: Virtual File Systems with a node fs-like API
Author: Konstantin Baierer
Latest version: 0.1.0

# vfs
A virtual filesystem that works like [fs](http://nodejs.org/api/fs.html)

[![Build Status](https://travis-ci.org/kba/fsvfs.svg?branch=master)](https://travis-ci.org/kba/fsvfs)

## Currently implemented

* `file` - a VFS that mirrors the local filesystem
* `zip` - a VFS on top of ZIP content
* `tar` - a VFS on top of tarball content (compressions: gzip, bzip2, xz)

## Creating a new VFS

* Subclass `vfs.base`
* Override
  * `_stat`
  * `_readdir`
npm package: @kbai/typed-ds
Description: Not trying to recreate `theme-ui`.
Latest version: 0.0.3

# Typed DS

Not trying to recreate `theme-ui`.

## Ideas

Maybe this project turns serves as a core-transpiler to CSS and other style specs for higher level style-languages and systems that rely on a strong typing.

Trying to explore

- CSS is probably too powerful 99% of the time. That means we should simplify the way we our UI for 99% of use cases. For example, design systems do this for "atoms" but could possibly simplify more complex stuff such as layout, handling selectors, and modifiers.
- Everything right now is loosely typed and checks are done on run-time. Clear tooling & developer experience improvements can be made with compile time checks
- Composing and augmenting themes are commonly done, but, it's not possible (that I know of) to maintain good type-checking if overrides are relied on global type merging. Type definitions should be modular and scoped.
- Can coming up with a more modular way to define UIs help solve no-code tools that have trouble managing complexity.
- Automatically aggregating front-end components in a project and being able to see visually see/modify variants and other properties

## Current usage

Example found in [typed-ds-samples](../typed-ds-samples/src/test1.ts)