open-index/open-npm huggingface dataset:
npm package: @heroku/update-node-build-script
Description: A one-time migration tool to help you get your builds running on Heroku with a single command
Author: Jeremy Morrell
Latest version: 1.0.3

@heroku/update-node-build-script
==========================

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/@heroku/update-node-build-script.svg)](https://www.npmjs.com/package/@heroku/update-node-build-script)

## Summary

You will need to make sure you are in your application's root directory, then run:

```
$ npx @heroku/update-node-build-script
```

## Why?

To make getting started with Node.js on Heroku easier we will begin executing the `build` script
by default if it is defined in your `package.json`. This change will go live on **Monday, March 11, 2019**.
Read more about this change in [our FAQ](https://help.heroku.com/P5IMU3MP/heroku-node-js-build-script-change-faq).

For users with an existing `build` script that they may not want run during the build, this will
require some slight modifications to their `package.json`. The modifications are simple and mechanical,
and this CLI tool will make updating as easy as possible.

![screenshot of the CLI tool working](https://user-images.githubusercontent.com/175496/52527554-3600c680-2c7f-11e9-8422-dba5aa9a03ba.png)

## Usage

You will need to make sure you are in your application's root directory, then run:

```
$ npx @heroku/update-node-build-script
```

`npx` is a tool that comes with the modern verions of `npm` bundled with Node. If for some reason, `npx`
is not available on your system, you can install it with the following command:

```
$ npm install -g npx
```

or download and run this package directly:

```
$ cd $APP_DIRECTORY
$ npm install -g @heroku/update-node-build-script
$ update-node-build-script
```

and then you can uninstall it when you are finished:

```
$ npm uninstall -g @heroku/update-node-build-script
```

## What does this command do?

When it runs it will inspect the contents of your `package.json` file, note which `scripts` you have defined,
and suggest a modification that will opt you in to the new build rules while maintaining your existing build behavior.

It will make no changes without your explicit approval.

![screenshot of the CLI tool working](https://user-images.githubusercontent.com/175496/52527554-3600c680-2c7f-11e9-8422-dba5aa9a03ba.png)

Feel free to inspect [the source of this tool](https://github.com/heroku/update-node-build-script/blob/master/src/index.js).

## I don't want to run an npx command on my system

No problem! This tool is provided only as a convenience. The changes are documented in [this FAQ](https://help.heroku.com/P5IMU3MP/heroku-node-js-build-script-change-faq)
and are simple to perform manually.
npm package: @heroku/worker-monitor
Description: a node worker process monitor
Author: Jonathan Clem
Latest version: 1.0.0

# worker-monitor

A module for monitoring the memory usage of Node worker processes, and killing
them when they reach a specified limit. This module is designed to be used in
conjunction with [clusterflock](https://github.com/jclem/clusterflock).

## Usage

Simply require and call `worker-monitor` for it to begin monitoring worker
processes:

```javascript
if (require('cluster').isWorker) {
  require('worker-monitor')();
}
```

### Options

The `worker-monitor` function accepts a few options:

- `disconnectTimeout` (Default: `5000`) The time after which a disconnecting
  worker will be immediately killed if it has failed to disconnect.
- `logPeriod` (Default: `10000`) The frequency with with a worker's memory usage
  will be logged.
- `monitorPeriod` (Default: `5000`) The frequency with with a worker's memory
  is monitored. This is when the worker will be killed if it exceeds
  `memoryLimit`.
- `memoryLimit` (Default: `220000000`) The limit (in bytes) that a worker's RSS
  may be.

For example:

```javascript
require('worker-monitor')({
  disconnectTimeout: 10000,
  logPeriod        : 5000
});
```

## Thanks, Heroku

While I created and maintain this project, it was done while I was an employee
of [Heroku][heroku] on the Human Interfaces Team, and they were kind enough to
allow me to open source the work. Heroku is awesome.

[heroku]: https://www.heroku.com/home