open-index/open-npm huggingface dataset:
npm package: @flaivour/apostrophe-enhancements
Description: ApostropheCMS 2 module which brings extended features to core modules
Author: Flaivour
Latest version: 1.0.1
Deprecated: false

# module
> ApostropheCMS 2 module which brings extended features to core modules

Well, ApostropheCMS is really great, but who does not want new features as fresh as beers in the freezer? 🍺

## Installation

Install module dependency
```bash
npm i --save @flaivour/apostrophe-enhancements
```

Declare it in apostrophe modules

```js
// Modules declaration into `app.js`
modules: {
  '@flaivour/apostrophe-enhancements': {}
}
```

That's it, module is ready 🎉

## Features

### Pieces insert conditions

Provide a way to declare conditions that new pieces must match to be inserted. These can be declared in `addConditions` property of piece options.

```javascript
// In declaration of module extending `apostrophe-pieces`
beforeConstruct: (self, options) => {
  options.addFields = [
    {
      name: 'price',
      label: 'Price',
      type: 'integer',
      required: true
    }
  ].concat(options.addFields || [])

  // Provide an array of conditions that should be match at insertion
  options.addConditions = [
    {
      label: 'price should be a valid number greater than 0',
      checking: (piece) => Number.isInteger(piece.price) && piece.price > 0
    }
  ].concat(options.addConditions || [])
}
```

`addConditions` is an array of conditions, taking form of objects containing at least a `matching` property. This last is a function that is going to be called in `beforeSave` with the insertion candidate piece. It must return a boolean, used to defined if condition is or not validated.

## License

This is released under the MIT License.
npm package: @flaivour/logger-pino
Description: ApostropheCMS 2 module which makes it use pino logger
Author: Flaivour
Latest version: 1.0.5
Deprecated: false

# logger-pino
> ApostropheCMS 2 module which makes it use pino logger

Pino is a very low overhead Node.js logger, inspired by Bunyan. This module make it usable as default logger for ApostropheCMS.

## Installation

Install module dependency
```bash
npm i --save @flaivour/logger-pino
```

Declare it in apostrophe modules

```js
// Modules declaration into `app.js`
modules: {
  '@flaivour/logger-pino': {}
}
```

That's it, module is ready 🎉

## Configuration

By default, all module options declared will be passed to the pino instance created for Apostrophe logs. Few of them are really interesting:

- `level` to define the minimum level from which the logs will actually be displayed in the terminal
- `prettyPrint` format and colors log outputs, more information at https://github.com/pinojs/pino-pretty

**Configuration example:**
```js
// Modules declaration into `app.js`
modules: {
  '@flaivour/logger-pino': {
    level: 'warn',
    prettyPrint: { colorize: true }
  }
}
```

## Usage

This module improve apostrophe-utils logging methods, which means it is totally transparent. Simply use `self.apos.utils.log()` to log message from anywhere.

## License

This is released under the MIT License.
npm package: @flaivour/releaser
Description: CLI tool to create changelogs and releases
Author: Flaivour
Latest version: 1.1.2
Deprecated: false

# Releaser
> CLI tool to create changelogs and releases 🤖

## About

**Releaser** is a command-line utility for organizing your changelog file that lists changes between application versions. It is intended to **NPM** based projects, and respects [keepachangelog](https://keepachangelog.com/en/1.0.0) format.

## Installation

`npm i --save-dev @flaivour/releaser`

You may define the following commands:

```javascript
// package.json
"scripts" : {
  "release": "releaser release",
  "changelog": "releaser changelog",
}
```

## Commands

- **changelog** [options] : Create changelog entry
- **release** [options] : Parse changelog entries and create new release

> You may use `--help` argument for more informations about usage and available flags.

### `changelog`

It creates a new changelog file at `changelogs/<branch>.json` describing the changes made by the current branch. Some questions will be asked for this purpose if the command is called without parameters.

### `release`

It retrieves files in `changelogs` to create a new release entry in `CHANGELOG.md`. This new version is computed by incrementing the one defined in `package.json` in a choosen way. Some questions will be asked for this purpose if the command is called without parameters.

## Licence

This is released under the MIT License.
npm package: @flakeed/react-yandex-maps
Description: Yandex.Maps API bindings for React
Author: Sergey Petushkov
Latest version: 4.6.0

# ⚠️ This project is archived

I am not interested in doing any free work for a company that is [helping Russia](https://www.proekt.media/narrative/yandex-i-kreml/) [to wage war on Ukraine](https://www.theguardian.com/world/2022/mar/30/western-owned-russian-firm-helps-sites-pushing-false-news-profit-from-ads-yandex) [by spreading state propaganda](https://www.protocol.com/policy/yandex-gershenzon-qa). This project is archived and will not get any updates

---

# react-yandex-maps

[Yandex.Maps JS API][ymaps-api] bindings for React

[ymaps-api]:
  https://tech.yandex.com/maps/doc/jsapi/2.1/quick-start/index-docpage/

## Documentation

~You can find the documentation at https://react-yandex-maps.now.sh~ This domain was claimed by another person and is not maintained by authors of this package anymore

## Contributing

Feel free to submit issues and/or PRs if you found bugs 🐞 or have some features
in mind! The documentation improvements will be super appreciated, if you feel
that docs are lacking in some places 📝👩‍🔬

### Developing locally (Quick Start)

If you want to work on the library locally:

1. Fork this repository and clone your version of the repo
2. Install npm dependencies

```sh
npm install
```

3. Start library build in the watch mode. This command will start microbundle in
   watch mode, meaning that everytime you make changes to the source of the
   library it will be compiled to `dist` folder

```sh
npm run dev
```

4. Install documentation dependencies

```sh
cd docs && npm install
```

5. Start docs server locally

```sh
npm run dev
```

If everything went well, you now have documentation running on
`http://localhost:3000`

You can find special sandbox page on
[`http://localhost:3000/sandbox`](http://localhost:3000/sandbox)

Now you can make changes to the library and see them applied to the sandbox in
real time.

When you commit changes, eslint will make sure that there are no linting errors
and prettier will format your code based on the repo settings.

When you push changes, jest will run a set of unit tests to make sure that all
of them are passing.

## License

[MIT](LICENSE)

## Kudos

Thanks to all [contributors][] for help with supporting the library

Thanks to [@effrenus](https://github.com/effrenus/) and his
[yandex-map-react](https://github.com/effrenus/yandex-map-react) for inspiring
this library

[contributors]: graphs/contributors
npm package: @flakey5/cache-control-parser
Description: A RFC9111-compliant cache control header parser.
Author: flakey5
Latest version: 1.0.0

# cache-control-parser

A [RFC9111-compliant](https://www.rfc-editor.org/rfc/rfc9111.html#name-cache-control) cache control header parser.

## Installing

`npm install @flakey5/cache-control-parser`

## Usage

### CJS
```javascript
const { parseCacheControlHeader } = require('@flakey5/cache-control-header')

const directives = parseCacheControlHeader('max-age=10, must-revalidate')
```

### ESM
```javascript
import { parseCacheControlHeader } from '@flakey5/cache-control-header'

const directives = parseCacheControlHeader('max-age=10, must-revalidate')
```

# License

This repository is licensed under the terms of the [MIT License](./LICENSE).
npm package: @flakey5/r2-localize
Description: Allows for serving files from different R2 buckets based on the request's region.
Author: flakey5
Latest version: 1.0.1

# r2-localize

Allows for serving files from different R2 buckets based on the request's region.

Primary use cases would be lowering latency or serving localized files.

## Usage

### Initializing

```typescript
const localizedBucket = localizeBucket({
  buckets: {
    wnam: env.WNAM_BUCKET,
    enam: env.ENAM_BUCKET,
    weur: env.WEUR_BUCKET,
    eeur: env.EEUR_BUCKET,
    apac: env.APAC_BUCKET,
  },
  // Region to use if one of the regions is undefined or we couldn't identify what region a colo is in/closest to
  fallbackRegion: 'wnam',
});
```

### Head

```typescript
// Heading a file
const object: R2Object | null = await localizedBucket.head('some-object', {
  request,
});
```

### Get

```typescript
const object: R2Object | R2ObjectBody | null = await localizedBucket.get(
  'some-object',
  {
    request,
    // R2GetOptions properties here, e.g.
    onlyIf: {
      // ...
    },
  }
);
```

### Put

Note: this puts the object in the nearest bucket only. The other buckets are unaffected.

```typescript
const object: R2Object | null = await localizedBucket.put(
  'some-object',
  'some-value',
  {
    request,
    // R2PutOptions properties here, e.g.
    onlyIf: {
      // ...
    },
  }
);
```

### CreateMultipartUpload

Note: this puts the object in the nearest bucket only. The other buckets are unaffected.

```typescript
const object: R2MultipartUpload = await localizedBucket.createMultipartUpload(
  'some-object',
  {
    request,
    // R2MultipartOptions properties here, e.g.
    httpMetadata: {
      // ...
    },
  }
);
```

### ResumeMultipartUpload

Note: this puts the object in the nearest bucket only. The other buckets are unaffected.

```typescript
const object: R2MultipartUpload = await localizedBucket.resumeMultipartUpload(
  'some-object',
  'upload id',
  { request }
);
```

### Delete

Note: this deletes the object in the nearest bucket only. The other buckets are unaffected.

```typescript
await localizedBucket.resumeMultipartUpload('some-object', 'upload id', {
  request,
});
```

### List

```typescript
const object: R2Objects = await localizedBucket.list({
  request,
  // R2ListOptions properties here, e.g.
  prefix: 'asd',
});
```

### Accessing a specific region

To access the bucket of a specific region, you can pass in the region's name instead of the request object.

```typescript
const object: R2Object | R2ObjectBody | null = await localizedBucket.get(
  'some-object',
  {
    region: 'wnam',
    // R2GetOptions properties here, e.g.
    onlyIf: {
      // ...
    },
  }
);
```

# License

This repository is licensed under the terms of the [MIT License](./LICENSE).
npm package: @flakiness-detective/utils
Description: Shared utilities for Flakiness Detective - Logger and common helpers
Author: prosdevlab
Latest version: 0.1.1

# @flakiness-detective/utils

Shared utilities and helper functions for Flakiness Detective.

## Overview

This package provides common utilities used across all Flakiness Detective packages, including logging, type definitions, and helper functions.

## Logger

A simple, configurable logger with multiple log levels.

### Usage

```typescript
import { createLogger } from "@flakiness-detective/utils";

const logger = createLogger({ level: "info" });

logger.log("Processing test failures...");
logger.log("Found 10 clusters");
```

### Log Levels

- `debug` - Detailed debugging information
- `info` - General informational messages (default)
- `warn` - Warning messages
- `error` - Error messages
- `silent` - No output

### Custom Logger Implementation

You can also implement your own logger:

```typescript
import type { Logger } from "@flakiness-detective/utils";

const customLogger: Logger = {
  log: (message: string) => {
    // Your custom logging logic
    console.log(`[CUSTOM] ${message}`);
  },
};
```

## API Reference

### `createLogger(options)`

Creates a logger instance with the specified configuration.

**Parameters**:

- `options.level` - Log level (`'debug'` | `'info'` | `'warn'` | `'error'` | `'silent'`)

**Returns**: `Logger` instance

### `Logger` Interface

```typescript
interface Logger {
  log(message: string): void;
}
```

## Examples

### Basic Logging

```typescript
import { createLogger } from "@flakiness-detective/utils";

const logger = createLogger({ level: "info" });

logger.log("Starting flakiness detection...");
logger.log("Analysis complete");
```

### Debug Mode

```typescript
import { createLogger } from "@flakiness-detective/utils";

const logger = createLogger({ level: "debug" });

logger.log("Fetching failures from database...");
logger.log("Generating embeddings...");
logger.log("Running DBSCAN clustering...");
```

### Silent Mode

```typescript
import { createLogger } from "@flakiness-detective/utils";

const logger = createLogger({ level: "silent" });

// No output
logger.log("This will not be logged");
```

## Integration

The `utils` package is used by all other Flakiness Detective packages:

- **Core**: For logging detection pipeline progress
- **Adapters**: For logging adapter operations (fetch, save, etc.)
- **CLI**: For user-facing output and verbose logging

## Related Packages

- **@flakiness-detective/core** - Core detection engine ([docs](../core/README.md))
- **@flakiness-detective/adapters** - Data adapters and embedding providers ([docs](../adapters/README.md))
- **@flakiness-detective/cli** - Command-line interface ([docs](../cli/README.md))

## License

MIT