open-index/open-npm huggingface dataset:
npm package: @gpolakow/native-watchdog
Description: A native module that kills the current process if the event loop is unresponsive
Author: Microsoft Corporation
Latest version: 0.3.2







# Watchdog node module
Kills the current process when the JavaScript event loop is busy for more than a configurable amount of time. e.g. an accidental while true loop.

This is implemented by launching a separate thread from C++ which periodically checks if an interval timer installed in the JavaScript event loop is fired.

> Note: The node module does not distinguish a never-completing operation from a long running operation that will eventually complete. If the event loop appears to be stuck and does not fire timers for a configurable period of time, the node module will terminate the process.

## Installing

```sh
npm install native-watchdog
```

## Using

```javascript
var watchdog = require('native-watchdog');

// Configures the module to kill the current process if the event loop
// is unresponsive for more than 5s.
watchdog.start(5000);
```

The module will print to `stderr` the JavaScript call stack at the time it detected the JavaScript event loop to be unresponsive and will exit the process with code 87 (unused by node.js):
```
The module native-watchdog has detected that the event loop is unresponsive.
Here is the JavaScript stack trace:
======================================native-watchdog======================================
bad (/Users/alex/src/node-native-watchdog/test/test.js:16:13)
good (/Users/alex/src/node-native-watchdog/test/test.js:21:5)
Timeout._onTimeout (/Users/alex/src/node-native-watchdog/test/test.js:24:5)
ontimeout (timers.js:386:14)
tryOnTimeout (timers.js:250:5)
Timer.listOnTimeout (timers.js:214:5)
======================================native-watchdog======================================
The module native-watchdog will now terminate the process with exit code 87.
```

## Developing
 * `npm install -g node-gyp`
 * `node-gyp configure`
 * `node-gyp build` (for debugging use `node-gyp build --debug`)
 * `npm test` (for debugging change `index.js` to load the node module from the `Debug` folder and press `F5`)

## Contributing

This project welcomes contributions and suggestions.  Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

## License
[MIT](https://github.com/Microsoft/node-native-watchdog/blob/master/LICENSE)
npm package: @gpsign/hyrax
Description: Hyrax is a small library I built for myself to make my life easier when working with TypeScript and React.
Author: gpsign
Latest version: 0.6.0

# Hyrax 
**My personal collection of utility functions and hooks for TypeScript & React**  

Hyrax is a small library I built for myself to make my life easier when working with TypeScript and React. It’s a grab bag of utility functions and custom hooks that I find useful across different projects. Instead of rewriting the same logic over and over, I decided to bundle them up into this little package.  

## Why? 🤔  
I got tired of copy-pasting the same helper functions and hooks across projects, so I put them all in one place. Now, I can just install Hyrax and get back to coding without the extra hassle.  

## What's Inside? 📦  
- Handy utility functions  
- Custom React hooks I use all the time  
- A little bit of everything to speed up development  
- Nothing fancy—just things that I personally find useful  

This isn’t meant to be a polished, production-ready library—it’s just my personal toolkit.
npm package: @gpt-flow/node
Description: Node.js middleware for logging errors to GPT-Flow
Latest version: 1.0.7


# @gpt-flow/node

A Node.js package to capture and send logs to the GPT-Flow API for processing and analysis.

## Step 1: Installation

Install the package using npm:

```bash
npm install @gpt-flow/node
```

## Step 2: Setting Up the Configuration

You have two options for setting up the configuration: using environment variables or configuring it programmatically.

### Option 1: Environment Variables

If you prefer to use environment variables, create a `.env` file in your project’s root directory and add the following variables:

```ini
PROJECT_ID=your_project_id
PUBLIC_KEY=your_public_key
PROJECT_URL=https://gpt-flow-llm-api.onrender.com
```

Make sure to replace the placeholders with your actual project details.

### Option 2: Programmatic Configuration

Alternatively, you can directly configure the package in your application code:

```javascript
const gptFlow = require('@gpt-flow/node');

// Initialize with your project settings
gptFlow.init({
    projectId: 'your_project_id',   // Replace with your project ID
    publicKey: 'your_public_key',   // Replace with your public key
    projectUrl: 'https://gpt-flow-llm-api.onrender.com',  // Replace with GPT-Flow URL
});
```

## Step 3: Using the Package in a Node.js Application

Once your configuration is set, you can use the GPT-Flow package to capture errors or logs in your Node.js application.

Here’s an example of how you could integrate it into an HTTP server:

```javascript
const http = require('http');
const gptFlow = require('@gpt-flow/node');

// Initialize GPT-Flow with your project configuration
gptFlow.init({
    projectId: process.env.PROJECT_ID || 'your_project_id',   // Replace with your project ID
    publicKey: process.env.PUBLIC_KEY || 'your_public_key',   // Replace with your public key
    projectUrl: process.env.PROJECT_URL || 'https://gpt-flow-llm-api.onrender.com',  // Replace with GPT-Flow URL
});

// Create a basic HTTP server
const server = http.createServer((req, res) => {
    if (req.url === '/') {
        // Simulate an error for logging purposes
        throw new Error('Simulated error for logging');
    }

    res.writeHead(200, { 'Content-Type': 'text/plain' });
    res.end('Hello, World!');
});

// Handle server errors and log them to GPT-Flow
server.on('error', (err) => {
    gptFlow.sendLogs({
        message: err.message,
        stack: err.stack,
        method: 'GET',
        url: '/',
    });
});

// Start the server
server.listen(3000, () => {
    console.log('Server is running on http://localhost:3000');
});
```

This setup will capture errors from your Node.js application and send the logs to the GPT-Flow API.
npm package: @gpt-flow/reactish
Description: An error-capturing component that captures errors and reports them to you as a human would.
Author: raul
Latest version: 0.1.13
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @gpt-flow/reactish

An error-capturing component that captures errors and reports them to you as a human would.

## Installation

Install the package via npm:

`npm install @gpt-flow/reactish`

## Usage

Wrap component in `GPT-Flow`

```ts
'use client'
import Users from "@/components/users";
import GptFlow from '@gpt-flow/reactish';

export default function Home() {
  return (
    <div className="grid grid-rows-[20px_1fr_20px] items-center justify-items-center min-h-screen p-8 pb-20 gap-16 sm:p-20 font-[family-name:var(--font-geist-sans)]">
      <main className="flex flex-col gap-8 row-start-2 items-center sm:items-start">
        <GptFlow projectId="your-project-id"
          publicKey="your-public-key"
          projectUrl='https://gpt-flow-llm-api-05w2.onrender.com'>
          <Users />
        </GptFlow>
      </main>
    </div>
  );
}
```

## Full Example

https://github.com/GPT-Flow/examples/tree/main/next
npm package: @gptmaker/n8n-nodes-gptmaker
Description: Custom n8n node for GPTMaker API
Author: Irrah Tech
Latest version: 1.0.5

# @gptmaker/n8n-nodes-gptmaker

Community node for the GPTMaker API.

Repository: https://github.com/irrahgroup/delaware-wilmington

## Features

- Native n8n resource/operation structure
- Bearer token authentication
- Dynamic dropdowns for Workspace and Agent
- Support for Workspace, Agent, Channel, Chat, Intention, Interaction, and Training resources
- Compatible with manual execution and multi-item workflows

## Supported Resources

### Workspace
- Get many workspaces
- Get workspace credits balance

### Agent
- Create, get, update, delete, activate, inactivate
- Conversation and context message actions
- Get credits spent
- Get/update settings
- Get/update webhooks

### Channel
- Create in agent or workspace context
- Get many by workspace
- Update/delete channel
- Get/update channel config

### Chat
- Get many chats by workspace
- List messages
- Send/edit/delete message
- Delete chat messages
- Delete chat
- Start/stop human support

### Intention
- List
- Create
- Update
- Delete

### Interaction
- List by workspace
- Delete

### Training
- Create
- Get many
- Update (TEXT)
- Delete

## Authentication

This node uses one credential:

- GPTMaker API
  - API Token

Token setup guide (official docs):

- https://developer.gptmaker.ai/api-reference/introduction#autentica%C3%A7%C3%A3o

Credential setup flow in n8n:

1. Create a new `GPTMaker API` credential.
2. Paste your GPTMaker API token into `API Token`.
3. Save and test the credential.

## Installation

```bash
npm install @gptmaker/n8n-nodes-gptmaker
```

Restart n8n after installation.

## Example Workflow

A sanitized workflow example is included at the project root:

- `workflow-example-gptmaker.json`

Use this file as a base for Creator Portal submission and internal QA.

## Publishing

Current release strategy: manual publish.

```bash
npm run lint
npm run build
npm publish --access public
```

Provenance-ready workflow is included for GitHub Actions:

- `.github/workflows/publish-provenance.yml`

It uses `npm publish --provenance --access public` and requires `NPM_TOKEN` in repository secrets.

## Development

```bash
npm run build
npm run dev
npm run lint
```

Project structure:

- `nodes/GptMaker/GptMaker.node.ts`: main node definition
- `nodes/GptMaker/GptMakerApi.credentials.ts`: credential definition
- `nodes/GptMaker/descriptions/`: node fields and operations
- `nodes/GptMaker/resources/`: execution logic
- `nodes/GptMaker/Helpers.ts`: shared API request helper

## License

MIT