open-index/open-npm huggingface dataset:
npm package: @israelcrux/gatsby-plugin-static-site
Description: A plugin that disables client side routing for gatsby
Author: Ward Peeters
Latest version: 0.4.0

# gatsby-plugin-static-site

Disables client side routing for Gatsby.
Completely stolen from: https://github.com/wardpeet/gatsby-plugin-static-site/pull/66
Cause we couldn't wait for this guy to merge.
Thanks however @wardpeet you and @cravi24 are awesome

## Install

`npm install --save @israelcrux/gatsby-plugin-static-site`

## How to use

```javascript
// In your gatsby-config.js
plugins: [`@israelcrux/gatsby-plugin-static-site`];
```
npm package: @israelnyc/cypress-control
Description: [![npm version](https://badge.fury.io/js/%40israelnyc%2Fcypress-control.svg)](https://badge.fury.io/js/%40israelnyc%2Fcypress-control)
Author: Israel Schulman
Latest version: 0.5.0

# Cypress Control

[![npm version](https://badge.fury.io/js/%40israelnyc%2Fcypress-control.svg)](https://badge.fury.io/js/%40israelnyc%2Fcypress-control)

Cypress Control adds a frontend to Cypress to start and stop Cypress, selectively run a subset of specs and to visualize the run in real-time.

![Completed Cypress Run](https://raw.githubusercontent.com/israelnyc/cypress-control/master/assets/images/completed_run_passing_failing_specs.png)

## Install

```bash
npm install @israelnyc/cypress-control
```

Require Cypress Control in a directory where Cypress is installed.

```javascript
const cypressControl = require('@israelnyc/cypress-control')();
```

## Runner

The runner can be started via the frontend but is also returned as a result of requiring and starting the server. So it can be started programatically.

```javascript
const cypressControl = require('@israelnyc/cypress-control')({
    port: 5000,
});

cypressControl.runner.start();
```

Along with the runner, the socket client and an object containing Cypress Control event constants are also returned, which allows for listening for the custom runner and reporter status events which the server emits.

```javascript
const cypressControl = require('@israelnyc/cypress-control')({
    port: 5000,
});

const { events, runner, socket } = cypressControl;

socket.on(events.CYPRESS_CONTROL_STATUS, data => {
    if (data.eventType === events.CYPRESS_CONTROL_TEST_END) {
        console.log('test ended');
    }
});

runner.start();
```

## Configuration

| Option | Description                         | Default |
| ------ | ----------------------------------- | ------- |
| `port` | Specify port to start the server on | 8686    |

## Runner Results

View runner results in real-time in the browser via the port the server was started on.
npm package: @iss-ai/extractor-core
Description: 一个通过jquery解析html页面工具,同时支持rss|atom|rdf|feedjson解析
Latest version: 0.0.5

# Page-Extractor
### Introduction
This is a sample Page Extractor!
The package is dependencies `axios`,`jquery`,`jsdom` In Node.js. And dependencies  `@iss-ai/chrome-extension-axios`,`jquery` in Chrome Extension.

#### Install
```shell
pnpm install @iss-ai/page-extractor
npm install @iss-ai/page-extractor
yarn add @iss-ai/page-extractor

#Node.js
pnpm install axios jquery jsdom

#Chrome Extension
pnpm install @iss-ai/chrome-extension-axios jquery

```
#### Used in Node.js
```javascript
import { DomPageExtractor, IPageExtractor, JsonPageExtractor } from '@iss-ai/page-extractor';
import { getJquery, setJquery,setAxios,getAxios } from '@iss-ai/page-extractor';
import axios from 'axios'
const {$,win}=createJqueryWin()
function createJqueryWin(){
  let jsdom = require('jsdom');  
  let dom =  new jsdom.JSDOM();  
  let window = dom.window;  
  let document = window.document; 
  let $ = require('jquery')(window);
  return {$,win:window}
}
const instance=getInstance()
function getInstance(){
  const instance = axios.create({
    timeout: 10000,
    withCredentials:true,
    headers: {
      'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36',
      'Accept':'text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7',
    }
  });
  instance.interceptors.response.use(function (response:any) {
    return response.data
  }, function (error:any) {
    return Promise.reject(error)
  })
  return instance
}
setJquery($,win)
setAxios(instance)
const sampleAxios=getAxios()
//static url
let url='https://xxx'
sampleAxios.get(url).then((res:any)=>{
  let extractor:IPageExtractor=new DomPageExtractor()
  let data=extractor.extractor(res)
  console.log('data-----',data)
})
//api url
url='https://xxx'
sampleAxios.get(url).then((res:any)=>{
  let extractor:IPageExtractor=new JsonPageExtractor()
  let data=extractor.extractor(res)
  console.log('data-----',data)
})
```
#### Used in ContentScript
```javascript
import { DomPageExtractor, IPageExtractor, JsonPageExtractor } from '@iss-ai/page-extractor';
import axios from '@iss-ai/chrome-extension-axios'
import $ from 'jquery'
import { getJquery, setJquery,setAxios,getAxios } from '@iss-ai/page-extractor';
setJquery($,window)
setAxios(axios)
const sampleAxios=getAxios()
//static url
let url='https://xxx'
sampleAxios.get(url).then((res:any)=>{
  let extractor:IPageExtractor=new DomPageExtractor()
  let data=extractor.extractor(res)
  console.log('data-----',data)
})
//api url
url='https://xxx'
sampleAxios.get(url).then((res:any)=>{
  let extractor:IPageExtractor=new JsonPageExtractor()
  let data=extractor.extractor(res)
  console.log('data-----',data)
})
```
npm package: @issaclau-org/learnstorybook-design-system
Description: The Storybook design system tutorial is a subset of the full [Storybook design system](https://github.com/storybookjs/design-system/), created as a learning resource for those interested in learning how to write and publish a design system using best in p
Latest version: 0.1.0

# Storybook design system tutorial

The Storybook design system tutorial is a subset of the full [Storybook design system](https://github.com/storybookjs/design-system/), created as a learning resource for those interested in learning how to write and publish a design system using best in practice techniques.

Learn more in [Storybook tutorials](https://storybook.js.org/tutorials/).
npm package: @issc29-org/actions-deploy-demo
Description: Functions for working with the Fibonacci sequence
Author: Bryan Cross
Latest version: 1.0.51

# fib-tools
a
![](https://github.com/bbq-beets/fib-tools/workflows/CI/badge.svg)

asdflkj

Make the magic happen

## Get the nth Number

```javascript
const {getNumber} = require('@bbq-beets/fib-tools')
assert.strictEqual(getNumber(8), 21)
```asdfasdfadsf

## Get a List of Numbers

```javascript
const {getList} = require('@bbq-beets/fib-tools')
assert.strictDeepEqual(getList(8), [0, 1, 1, 2, 3, 5, 8, 13, 21])
```

## Get a Sequence of Numbers

```javascript
const {getSequence} = require('@bbq-beets/fib-tools')

const seq = getSequence()

for (const n of seq) {
  console.log(n) // The next Fibonacci number in the sequence
}
```
npm package: @issimo/add-history-listener
Description: Subscribe to browser history.
Latest version: 1.0.0

This package provides a simple api to subscribe to browser history events.

# add-history-listener

[![size](https://img.shields.io/bundlephobia/minzip/@issimo/add-history-listener)](https://bundlephobia.com/result?p=@issimo/add-history-listener)
[![downloads](https://img.shields.io/npm/dw/@issimo/add-history-listener)](https://www.npmjs.com/package/@issimo/add-history-listener)
[![npm](https://img.shields.io/npm/v/@issimo/add-history-listener)](https://www.npmjs.com/package/@issimo/add-history-listener)
[![GitHub](https://img.shields.io/github/license/issimoteam/add-history-listener)](https://github.com/issimoteam/add-history-listener)

This package provides a simple API to subscribe to browser history events.

```ts
const cleanup = addHistoryListener((prev, next) => {
  console.log(next);
});

history.replaceState(42, undefined, "/somewhere#over-the-rainbow");
// Prints { state: 42, pathname: "/somewhere", hash: "#over-the-rainbow", ...other useful things}
```
npm package: @issimo/await-timeout
Description: It's setTimout but you can await it.
Latest version: 1.0.0

It's setTimout but you can await it.

[![size](https://img.shields.io/bundlephobia/minzip/@issimo/await-timeout)](https://bundlephobia.com/result?p=@issimo/await-timeout)
[![downloads](https://img.shields.io/npm/dw/@issimo/await-timeout)](https://www.npmjs.com/package/@issimo/await-timeout)
[![npm](https://img.shields.io/npm/v/@issimo/await-timeout)](https://www.npmjs.com/package/@issimo/await-timeout)
[![GitHub](https://img.shields.io/github/license/issimoteam/await-timeout)](https://github.com/issimoteam/await-timeout)

# await-timeout

It's literally just this:

```ts
export default function Timeout(ms: number): Promise<void> {
  return new Promise((resolve) => setTimeout(() => resolve(), ms));
}
```
npm package: @issimo/deep-state
Description: A simple state store. Performs a deep comparison before calling the callbacks.
Latest version: 1.0.0

A simple state store. Performs a deep comparison before calling the callbacks.

[![size](https://img.shields.io/bundlephobia/minzip/@sebastbake/deep-state)](https://bundlephobia.com/result?p=@sebastbake/deep-state)
[![downloads](https://img.shields.io/npm/dw/@sebastbake/deep-state)](https://www.npmjs.com/package/@sebastbake/deep-state)
[![npm](https://img.shields.io/npm/v/@sebastbake/deep-state)](https://www.npmjs.com/package/@sebastbake/deep-state)
[![GitHub](https://img.shields.io/github/license/sebastbake/deep-state)](https://github.com/SebastBake/deep-state)

```ts
const state = State();

const cleanup = state.subscribe((prev, next) => {
  // stuff
});

state.value = { foo: "bar" }; // trigger callback
state.value = { foo: "bar" }; // nothing
```
npm package: @issos1993/flow-random
Description: A library that help to flow control by a random number
Author: Lucas Barbosa
Latest version: 1.1.7

# flow-random-js

flow-random-js is a library for generating random flows based on probabilities.

## Installation

To install flow-random-js into your project, you can use npm:

```bash
npm install flow-random
```

## Usage

```javascript
import { flowRandom } from 'flow-random';

// Generate a random flow with a custom probability (optional, default is 100)
const resultado = flowRandom(); // Returns `true` or `false` based on probability
console.log(resultado); // Result of the random flow
```
## Params

probability (optional): An integer representing the probability for the flow to be true. Default is 100.

## Example

```javascript
// Generate a random flow with a 75% probability
const resultado = flowRandom(75); // Returns `true` or `false` based on probability
console.log(resultado); // Result of the random flow
```

## Contributing

Feel free to contribute to this library! If you have suggestions, issues, or enhancements, please open an issue or a pull request.

## License

This project is licensed under the [MIT License](https://choosealicense.com/licenses/mit/).
npm package: @issr/babel-plugin
Description: Babel plugin for iSSR
Author: Aleksandrov Sergey
Latest version: 4.0.1

<p align="center">
  <img alt="iSSR" src="http://natrube.net/issr/logo.svg">
</p>

The easiest way to move your React application to Server-Side Rendering. Handles Side Effects and synchronizes State.

[README](https://github.com/AlexSergey/issr)

## Articles
- [ENG: Server-Side Rendering from zero to hero](https://dev.to/alexsergey/server-side-rendering-from-zero-to-hero-2610)
- [RU: Server-Side Rendering с нуля до профи](https://habr.com/ru/post/527310/)

## Features
- TypeScript support
- React 19 and React-Compiler support
- Small size (5kb)
- Without dependencies
- **iSSR** supports native setState, Redux (thunk, sagas), Mobx, Apollo and other state management libraries

## The MIT License

Copyright (c) Aleksandrov Sergey

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
npm package: @issr/core
Description: iSSR the easiest way to move your React application to Server Side Rendering
Author: Aleksandrov Sergey
Latest version: 4.0.1

<p align="center">
  <img alt="iSSR" src="http://natrube.net/issr/logo.svg">
</p>

The easiest way to move your React application to Server-Side Rendering. Handles Side Effects and synchronizes State.

[README](https://github.com/AlexSergey/issr)

## Articles
- [ENG: Server-Side Rendering from zero to hero](https://dev.to/alexsergey/server-side-rendering-from-zero-to-hero-2610)
- [RU: Server-Side Rendering с нуля до профи](https://habr.com/ru/post/527310/)

## Features
- TypeScript support
- Small size (5kb)
- Without dependencies
- **iSSR** supports native setState, Redux (thunk, sagas), Mobx, Apollo and other state management libraries

## The MIT License

Copyright (c) Aleksandrov Sergey

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
npm package: @issue-reporter/core
Description: Shared contracts, schemas, and formatting helpers for IssueReporter
Latest version: 0.1.9

# @issue-reporter/core

Shared contracts, schemas, and formatting helpers for IssueReporter.

## Install

```bash
npm install @issue-reporter/core
```

## What It Includes

- request and response contracts
- shared error codes
- Zod-backed schemas
- issue title/body formatting helpers
- asset URL helpers

## Smallest Useful Example

```ts
import {
  buildIssueReportBody,
  buildIssueReportTitle,
  issueReportSubmissionSchema,
} from '@issue-reporter/core';

const parsed = issueReportSubmissionSchema.parse(input);
const title = buildIssueReportTitle(parsed);
const body = buildIssueReportBody({
  submission: parsed,
  screenshotUrl: 'https://cdn.example.com/report.png',
});
```

## Limitations

This package is meant to support the `@issue-reporter/react` and `@issue-reporter/fastify` packages. It is not intended as a general-purpose issue-tracking toolkit.

## More

- Repo docs: <https://github.com/AndyK888/IssueReporter>
- React package: `@issue-reporter/react`
- Fastify package: `@issue-reporter/fastify`
npm package: @issue-reporter/fastify
Description: Fastify routes and adapters for IssueReporter backends
Latest version: 0.1.9

# @issue-reporter/fastify

Experimental Fastify plugin and backend adapters for IssueReporter.

## Install

```bash
npm install @issue-reporter/fastify @issue-reporter/core fastify
```

## Smallest Useful Example

```ts
import Fastify from 'fastify';
import {
  createGitHubIssueSink,
  createS3CompatibleStorage,
  issueReporterPlugin,
} from '@issue-reporter/fastify';

const app = Fastify();

await app.register(issueReporterPlugin, {
  routePrefix: '/issue-reports',
  enabled: true,
  issueSink: createGitHubIssueSink({
    token: process.env.ISSUE_REPORTER_GITHUB_TOKEN!,
    owner: process.env.ISSUE_REPORTER_GITHUB_OWNER!,
    repo: process.env.ISSUE_REPORTER_GITHUB_REPO!,
  }),
  storage: createS3CompatibleStorage({
    provider: 's3',
    endpoint: process.env.ISSUE_REPORTER_S3_ENDPOINT!,
    region: process.env.ISSUE_REPORTER_S3_REGION ?? 'auto',
    bucket: process.env.ISSUE_REPORTER_S3_BUCKET!,
    accessKeyId: process.env.ISSUE_REPORTER_S3_ACCESS_KEY_ID!,
    secretAccessKey: process.env.ISSUE_REPORTER_S3_SECRET_ACCESS_KEY!,
    routePrefix: '/issue-reports',
  }),
});
```

If your frontend calls `/api/issue-reports`, either mount the plugin there or
add a proxy/rewrite from `/api/issue-reports` to `/issue-reports`.

## Limitations

- Experimental `0.x` API
- currently targeted at Fastify only
- production setups still need auth and GitHub configuration
- storage is only required when you want captured or manual image evidence to be
  uploaded

## Status and storage

`GET /issue-reports/status` returns capability information that the React UI uses to choose
between captured, manual, and no-screenshot flows.

If you omit storage, the plugin can still serve no-screenshot reports, but it
will report that image-backed evidence is unavailable.

## More

- Detailed setup is documented in the project repository's `docs/fastify-setup.md`.
- A runnable example lives in the `demo-api` workspace in the project repository.
npm package: @issue-reporter/react
Description: React components and browser capture flow for IssueReporter
Latest version: 0.2.0

# @issue-reporter/react

Experimental React UI and browser capture flow for IssueReporter.

The current reporter opens in a responsive Precision Glass shell: wide layouts keep a left screenshot workspace beside a right details rail, narrow layouts stack the same workspace above the rail, the screenshot workspace uses the marker.js editor as a dedicated image-markup tool, and footer capture or submit actions sit below the shell chrome.

## Install

```bash
npm install @issue-reporter/react @issue-reporter/core
```

Peer dependencies:

- `react@19.x`
- `react-dom@19.x`

## Smallest Useful Example

```tsx
import {
  IssueReportDialog,
  IssueReportLauncher,
  IssueReporterProvider,
  createIssueReporterApiClient,
} from '@issue-reporter/react';

const apiClient = createIssueReporterApiClient({
  baseUrl: '/api/issue-reports',
});

export function AppShell() {
  return (
    <IssueReporterProvider apiClient={apiClient} appVersion="1.2.3">
      <main data-issue-report-capture-root="true">
        <YourApp />
      </main>
      <IssueReportLauncher />
      <IssueReportDialog />
    </IssueReporterProvider>
  );
}
```

## Default Popup Behavior

- The popup shell is responsive: wide layouts keep the screenshot workspace beside the details rail, while narrow layouts stack the same workspace and rail vertically.
- Screenshot markup runs through marker.js: the workspace mounts the marker.js editor as a dedicated image-markup tool instead of the previous in-house annotation canvas.
- Recovery stays in the details rail: retry true capture, paste or upload a screenshot manually, or continue with a comment-only report when screenshots are unavailable.
- Successful submissions reflect the chosen evidence path so users can tell whether the report included a captured screenshot, manual screenshot evidence, or comments only.

## Limitations

- Experimental `0.x` API
- best capture results come from recent Chrome desktop builds
- native Chrome capture temporarily isolates the selected capture root with `isolation: isolate`
- browsers without the native capture APIs use DOM capture fallback
- supported Chrome runtime capture failures surface inside the details-rail recovery ladder instead of silently downgrading to DOM capture
- the current recommended path is the provider + launcher + dialog composition shown above

## More

- Detailed setup is documented in the project repository's `docs/react-setup.md`.
- A runnable example lives in the `demo-web` workspace in the project repository.
npm package: @issuekit/core
Description: ```javascript const { Issuekit } = require('@issuekit/core') const issuekit =  new Issuekit({   auth: '0000000000000000000000000000000000000000',   repo: 'issuekit/core.js',   issue: '42' }) ``` ### Comment on an issue: ```javascript issuekit.addComment('
Latest version: 0.2.0

# @issuekit/core.js
## Usage:
### Setup:
```javascript
const { Issuekit } = require('@issuekit/core')
const issuekit =  new Issuekit({
  auth: '0000000000000000000000000000000000000000',
  repo: 'issuekit/core.js',
  issue: '42'
})
```
### Comment on an issue:
```javascript
issuekit.addComment('Hello World')
```
### Add labels to an issue
```javascript
issuekit.addLabels(['hello', 'world'])
```

### Add Assignees to an issue
```javascript
issuekit.addAssignees(['issuekit', 'nthnchu'])
```
npm package: @ist-402-group-1/fphhbutton
Description: Webcomponent fphhbuttonfp-hh-button following open-wc recommendations
Author: fphhbuttonfp-hh-button
Latest version: 0.0.1

# \<fphhbuttonfp-hh-button>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

## Installation

```bash
npm i fphhbuttonfp-hh-button
```

## Usage

```html
<script type="module">
  import 'fphhbuttonfp-hh-button/fphhbuttonfp-hh-button.js';
</script>

<fphhbuttonfp-hh-button></fphhbuttonfp-hh-button>
```

## Linting and formatting

To scan the project for linting and formatting errors, run

```bash
npm run lint
```

To automatically fix linting and formatting errors, run

```bash
npm run format
```

## Testing with Web Test Runner

To execute a single test run:

```bash
npm run test
```

To run the tests in interactive watch mode run:

```bash
npm run test:watch
```

## Demoing with Storybook

To run a local instance of Storybook for your component, run

```bash
npm run storybook
```

To build a production version of Storybook, run

```bash
npm run storybook:build
```


## Tooling configs

For most of the tools, the configuration is in the `package.json` to minimize the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `web-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`
npm package: @ist-402-group-1/kmbtn
Description: Webcomponent anything-under-the-sun following open-wc recommendations
Author: anything-under-the-sun
Latest version: 0.0.1

# \<anything-under-the-sun>

This webcomponent follows the [open-wc](https://github.com/open-wc/open-wc) recommendation.

## Installation

```bash
npm i anything-under-the-sun
```

## Usage

```html
<script type="module">
  import 'anything-under-the-sun/anything-under-the-sun.js';
</script>

<anything-under-the-sun></anything-under-the-sun>
```

## Linting and formatting

To scan the project for linting and formatting errors, run

```bash
npm run lint
```

To automatically fix linting and formatting errors, run

```bash
npm run format
```

## Testing with Web Test Runner

To execute a single test run:

```bash
npm run test
```

To run the tests in interactive watch mode run:

```bash
npm run test:watch
```

## Demoing with Storybook

To run a local instance of Storybook for your component, run

```bash
npm run storybook
```

To build a production version of Storybook, run

```bash
npm run storybook:build
```


## Tooling configs

For most of the tools, the configuration is in the `package.json` to minimize the amount of files in your project.

If you customize the configuration a lot, you can consider moving them to individual files.

## Local Demo with `web-dev-server`

```bash
npm start
```

To run a local development server that serves the basic demo located in `demo/index.html`