open-index/open-npm huggingface dataset:
npm package: @onehilltech/gatekeeper-cli
Description: command-line interface for Gatekeeper
Latest version: 0.3.0

gatekeeper-cli
==============

command-line interface for Gatekeeper

[![npm version](https://img.shields.io/npm/v/@onehilltech/gatekeeper-cli.svg?maxAge=2592000)](https://www.npmjs.com/package/@onehilltech/gatekeeper-cli)
[![Build Status](https://travis-ci.org/onehilltech/gatekeeper-cli.svg?branch=master)](https://travis-ci.org/onehilltech/gatekeeper-cli)
[![Dependencies](https://david-dm.org/onehilltech/gatekeeper-cli.svg)](https://david-dm.org/onehilltech/gatekeeper-cli)
[![Coverage Status](https://coveralls.io/repos/github/onehilltech/gatekeeper-cli/badge.svg?branch=master)](https://coveralls.io/github/onehilltech/gatekeeper-cli?branch=master)

Installation
--------------

    npm install -g @onehilltech/gatekeeper-cli
 
Getting Started
---------------

First, we need to setup Gatekeeper from the Blueprint application directory:

    ./bin/gatekeeper-setup
    
This will register the `gatekeeper-cli` with the current service, and allow you
to run the `gatekeeper-cli` to manage what client and account has access to your
service.

### Adding a client

Each client (i.e., mobile app, web portal, etc.) must be registered with the service
to be allowed access. We can register a new client with the service as follows:

    gatekeeper client add --base <base-uri> <name> <email> [scope]
    
where `scope` is an optional list of strings that define the access scope for the
client (`*` denotes superuser). The client id and secret will be printed to the
console. This should be used with requesting a client-level access token from the
service.

### Adding a user account

It is also possible to add a user account to the service. The user account represents
an individual who has access to the service. Similar to adding a client, you can add
a user account:

    gatekeeper account add --base <base-uri>
    
Follow the on-screen prompts to complete the addition process. The `username` 
and `password` are used to create an access token for the user.

Next Steps
----------

For more details, use the `--help` option.

Happy Coding!
npm package: @onehoax/biome
Description: Base Biome config
Author: Andres Osorio
Latest version: 0.0.2

# Description 

This package serves as the base `biome` rules for `javascript` projects.  
It can easily be extended/overridden.  
Its dependencies are fixed for stability and should be upgraded with a tool like [Renovate](https://docs.renovatebot.com/).  

# Installation

1. Uninstall any linting/formatting related packages (`eslint`, `prettier`, etc.)

2. Install the following as dev dependencies:
    ```bash
    npm install -D @onehoax/biome
    ```

# Configuration

1. Remove existing linting/formatting config files

2. Create a `biome.js` on the project's root directory and place the following contents inside:
    ```json
    {
      "extends": ["@onehoax/biome/base"]
    }
    ```

## Overriding configs

`@onehoax/biome/base` exports a `JSON` object with `biome` options;
you can extend/override these options by adding more options to your `biome.js` file:
```json
{
  "extends": ["@onehoax/biome/base"],
  "files": {
    "include": ["..."],
    "ignore": ["..."]
  },
  "linter": {
    "rules": {
      ...
    }
  },
  ...
}
```

# Run

Add the following script to your `package.json`:
```json
{
  ...,
  "scripts": {
    ...,
    "biome:check": "pnpm biome check ./",
    "biome:format": "pnpm biome format --write ./",
    "biome:lint": "pnpm biome lint --write ./",
    "biome:fix": "pnpm biome check --write ./"
  },
  ...
}
```

All the commands run against the files specied in the config (this package specifies `["./src/**/*.js", "./test/**/*.js"]`).  
- `pnpm run biome:check` -> runs formatter, linter and import sorting to the requested files; only reports
- `pnpm run biome:fix` -> runs formatter, linter and import sorting to the requested files; writes changes
- `pnpm run biome:format` -> runs formatter to the requested files; writes changes
- `pnpm run biome:lint` -> runs linter to the requested files; writes changes

### Future Goals

The goal is to integrate the formatting into commit workflow and the `CI/CD` pipelines.

# References

- [Biome](https://biomejs.dev)

# TODO 

- [ ] Integrate as part commit workflow ([`Husky`](https://typicode.github.io/husky/) and [`pre-commit hooks`](https://prettier.io/docs/en/precommit))
- [ ] Integrate as part of CI/CD  
- [ ] Automate dependency upgrade dependencies with [Renovate](https://docs.renovatebot.com/)