open-index/open-npm huggingface dataset:
npm package: @gridonic/generator
Description: Our yeoman generator.
Author: Gridonic
Latest version: 2.2.1

<p align="center">
    <img src="https://raw.githubusercontent.com/yeoman/media/master/optimized/yeoman-horizontal.png" width="420" alt="Yeoman"><br><br>
    Our <strong>opinionated</strong> <a href="https://yeoman.io/">Yeoman</a> generator.
</p>
<br>

## Installation

It’s advised to install it globally. Just run `$ npm install --global @gridonic/generator`.

<br>

## How to use?

Since the generator exposes a set of commands and flags to our [@gridonic/cli](https://github.com/gridonic/cli) you can get an overview of all commands by running `$ gridonic` within your shell.

#  
<p align="center">
  <a href="https://gridonic.ch">gridonic.ch</a> ・
  <a href="https://gridonic.github.io">gridonic.github.io</a> ・
  <a href="https://twitter.com/gridonic">@gridonic</a>
</p>

## Publishing

When ready to release, execute the following steps, given that all changes are commited in the master branch:
- List changes in the CHANGELOG.md
- Bump your version and automatically create a git tag with `npm version <type>`, where type is patch, minor or major
- Push the master branch `git push` and the tags `git push --tags`
- Create a release in github. A github action will then automatically publish the package to npm


[@gridonic/cli]: https://github.com/gridonic/cli
npm package: @gridonic/log
Description: Consistent console logging.
Author: Gridonic
Latest version: 1.0.0

<p align="center">
  <img width="240" src="https://gridonic.github.io/assets/images/logos/gridonic.svg"><br>
  Consistent console logging for our CLI apps.
</p>

<br>

## Installation

Very simple. Just run `$ npm install @gridonic/log`.

<br>

## How to use?

Examples say more than a thousand words.

```js
const { info, error, success, warning } = require('@gridonic/log');

try {
    info('Starting my app…');
    
    if (specialCondition() === true) {
        warning('Please pay attention to this.');
    }
    
    // Make sure success message has enough blank space before it
    success('Everything done.', 0, 3);
} catch(myBadError) {
    error(myBadError);
}
```

You may also use the **second** (`newlineAfter`)  and **third** (`newlineBefore`) parameter for adding newlines.

#  
<p align="center">
  <a href="https://gridonic.ch">gridonic.ch</a> ・
  <a href="https://gridonic.github.io">gridonic.github.io</a> ・
  <a href="https://twitter.com/gridonic">@gridonic</a>
</p>
npm package: @gridpro/node-cleaner
Description: Analyze disk usage by node_modules
Author: Gridpro
Latest version: 1.0.4

# node-cleaner
Analyze disk usage by node_modules

## Installation & Usage

```bash
npx @gridpro/node-cleaner
# or
npm install -g @gridpro/node-cleaner
node-cleaner
```
## License

MIT
npm package: @gridql/kafka-event-consumer
Description: Listens to mongo and emits events
Author: Tom Marsh
Latest version: 3.9.0

# Kafka Event Consumer

The grid is made up of multiple event stores. We have two primary ways of those events being generated:

- user action
  - HTTP Request via the REST API
- system reaction
  - Taking events from a queue

This modules focuses on the latter.

In principle _all_ we have to do is:

- Take event from queue
- Discriminate based on operation type
- Forward to RestAPI

## TODO

### Features

- [x] Basic happy path
  - [x] CREATE
  - [x] DELETE
  - [x] UPDATE
- [x] Work with any field as "ID"
- [x] Split message out of envelope
- [ ] Bulk changes
- [x] Default to picking up where the group left off
- [ ] Sad path
  - [ ] Dead letter queue
  - [x] validation of message
  - [ ] Handling network outages

### NFRs

- [ ] Performance tests
- [ ] Integration test
npm package: @gridql/payload-generator
Description: ## Usage
Latest version: 3.8.4

# Payload Generator

## Usage

```js
const { builderFactory } = require("@gridql/payload-generator");

const schema = {
  type: "object",
  properties: {
    _id: {
      type: "string",
      format: "id",
    },
  },
  required: ["_id"],
  additionalProperties: false,
};

const bf = builderFactory(schema);

let testThing = bf();

let manyThings = bf(1000);
```

Check out the tests for other ideas.
npm package: @gridscale/getsandbox-express
Description: getsandbox-express adapter and cli
Author: xbtsw
Latest version: 1.1.7

# @gridscale/getsandbox-express
A getsandbox.com to express adapter

## About this fork
* This fork introduces a change to the `require` function, used in the sandbox modules. 
It will execute the code of the required files within a VM, getting an identical context (but not the same!) as the main sandbox script. This enables required modules to use 3rd party modules like lodash and moment and the state. And that enables you to split your sandbox into multiple files. 

* This fork provides the possibility to make the state persistent. Therefore a third parameter `options` is introduced to the `loadSandbox` function. Set property `persistState` to true, will create a `state.json` file next to your sandbox main script. This file will be updated with the current state every second. When restarting the sandbox, it will search for this file and try to restore the state from it's content.

* `console` object is available in modules - so logging can be done


## Usage

### as command-line tool, without installing

```bash
npx @gridscale/getsandbox-express <main.js> [<port>]
```

Alternatively, if you want to install it globally:

```bash
npm install -g @gridscale/getsandbox-express
sandbox <main.js> [<port>]
```

Default port is `8080`.

### as Node.js module

```js
const sandbox = require('@gridscale/getsandbox-express')
const express = require('express')

const app = express()
sandbox.loadSandbox(app, __dirname + '/mysandbox/main.js')

const port = 8080
app.listen(port, () => {
  console.log(`Sandbox listening on port ${port}.`)
})
```