open-index/open-npm huggingface dataset:
npm package: @navneetlal/react-jdenticon
Description: React component to easily include jdenticon created image in project
Author: navneetlal
Latest version: 1.0.0

# react-jdenticon

> React component to easily include jdenticon created image in project

[![NPM](https://img.shields.io/npm/v/react-jdenticon.svg)](https://www.npmjs.com/package/react-jdenticon) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save react-jdenticon
```

## Usage

```tsx
import React, { Component } from 'react'

import MyComponent from 'react-jdenticon'
import 'react-jdenticon/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
```

## License

MIT © [navneetlal](https://github.com/navneetlal)
npm package: @navneetlal/xml-middleware
Description: XML middleware for expressjs to provide support for xml with easy setup
Author: Navneet Lal Gupta
Latest version: 0.1.1

# XML Middleware

A simple middleware for expressjs which allow an easy setup for xml support. Apart from that it also provides a standard response object for consistency.

## Installing

Using npm:

```bash
npm install @navneetlal/xml-middleware --save
```

Using yarn:

```bash
yarn add @navneetlal/xml-middleware
```

## Usage

`body-parser` or other (which can parse request body to text) is required for this middleware to work.

### CommonJS usage

```js
const xmlMiddleware = require('@navneetlal/xml-middleware');
const { text as textParserMiddleware } = require('body-parser');

app.use(textParserMiddleware({ type: ['xml', '+xml', 'text/xml'] }));
app.use(xmlMiddleware());
```

Now in order to send response, use `res.sendResponse()` instead of standard method provided by express.

You can also make use of `ServerResponse` class to construct a response object

```js
const responseObject = new ServerResponse(true, 'Success')
responseObject.results = { some: 'json' }

res.sendResponse(responseObject)
res.sendResponse(400, new ServerResponse(false, 'Oops! Somethings doesn\'t look right'))
```

### Typescript usage

This package is built on typescript and provides full support for the same.

## Issues

In case of any problem in the package open an issue here at [https://github.com/navneetlal/xml-middleware-expressjs/issues](https://github.com/navneetlal/xml-middleware-expressjs/issues)
npm package: @navnkmr08/wdio-slack-ci-reporter
Description: Unified WDIO + Allure + BrowserStack → Slack reporter. CLI, template renderer, BS session export, optional Slack file uploads, tests, linting, schema validation, semantic-release.
Latest version: 0.1.0

# @navnkmr08/wdio-slack-ci-reporter

## Install

```bash
npm i -D @navnkmr08/wdio-slack-ci-reporter
```

## WDIO hook (multiple spec files supported)

Each WDIO worker calls `bs-record` in `afterSession`, appending one NDJSON row per session. The CLI later reads **all** rows.

```js
const { execSync } = require('node:child_process');
afterSession: async function (config, capabilities, specs) {
  try {
    const id = global.browser?.sessionId || browser.sessionId;
    const specName = specs && specs[0] ? specs[0].split('/').pop() : undefined;
    execSync(`npx bs-record --session-id ${id} --spec "${specs?.[0] || ''}" --spec-name "${specName || ''}"`, { stdio: 'inherit' });
  } catch (e) { console.error('bs-record failed', e); }
}
```

### Heavy parallelism? Merge per-worker files

When running many specs in parallel, prefer **per-worker** files (e.g., `bs-videos-$WORKER_ID.ndjson`) and merge:

```bash
npx merge-ndjson bs-videos-*.ndjson --out bs-videos.ndjson --sort-by time
```

## Slack from Jenkins (parameters → template vars) + export BS JSON + upload files

```bash
JSON=$(npx slack-ci \
  --template slack-template.json \
  --schema schema/slack-template.schema.json \
  --allure-summary allure-report/widgets/summary.json \
  --videos bs-videos.ndjson \
  --param JOB_NAME="${JOB_NAME#GAMES/}" \
  --param TEST_SUITE="automation-qa" \
  --param PLATFORM="${platform}" \
  --param ENVIRONMENT="${runner}" \
  --param REGION="${region}" \
  --param ALLURE_URL="${ALLURE_URL}" \
  --param JENKINS_URL="${BUILD_URL}" \
  --param BROWSERSTACK_OBSERVABILITY_URL="${BROWSERSTACK_OBSERVABILITY_URL}" \
  --max-videos 10 \
  --bs-export bs-json \
  --slack-token "$SLACK_BOT_TOKEN" \
  --slack-channel "$SLACK_CHANNEL_ID" \
  --thread-ts "$SLACK_THREAD_TS" \
)
echo "$JSON" > payload.json
curl -sS -X POST -H 'Content-Type: application/json' --data @payload.json "$SLACK_WEBHOOK"
```

## GitHub templates

- `.github/ISSUE_TEMPLATE/bug_report.yml`
- `.github/ISSUE_TEMPLATE/feature_request.yml`
- `.github/pull_request_template.md`

## CHANGELOG & release

- Seeded `CHANGELOG.md`
- `.releaserc.cjs` configured for notes formatting and npm+GitHub publishing via `semantic-release`
npm package: @navoio/warehouse
Description: JavaScript and Node client for accessing Navo Warehouse data.
Author: Navo
Latest version: 0.5.1

# Navo Warehouse JS Client [![Actions Status](https://github.com/navoio/warehouse-js/workflows/Node%20CI/badge.svg)](https://github.com/navoio/warehouse-js/actions)
JavaScript and Node client for accessing [Navo Warehouse](https://navo.io/products/warehouse/) data.

## Install
```bash
yarn add @navoio/warehouse
# or
npm install @navoio/warehouse
```

## Authentication
```js
import { NavoClient } from '@navoio/warehouse';

// Option 1- pass credentials into constructor
const client = new NavoClient(apiUrl, 'client-id', 'api-key');

// Option 2- call authorize() manually
const client = new NavoClient(apiUrl);
client.authorize('client-id', 'api-key');
```

## Jobs
Get all active jobs:
```js
const jobs = await client.jobs.getAll();
```

Get a single job by job id:
```js
const job = client.jobs.get(1);
```