open-index/open-npm huggingface dataset:
npm package: @superhuman/react-dom
Description: React package for working with the DOM.
Latest version: 16.1.1

# `react-dom`

This package serves as the entry point of the DOM-related rendering paths. It is intended to be paired with the isomorphic React, which will be shipped as `react` to npm.

## Installation

```sh
npm install react react-dom
```

## Usage

### In the browser

```js
var React = require('react');
var ReactDOM = require('react-dom');

class MyComponent extends React.Component {
  render() {
    return <div>Hello World</div>;
  }
}

ReactDOM.render(<MyComponent />, node);
```

### On the server

```js
var React = require('react');
var ReactDOMServer = require('react-dom/server');

class MyComponent extends React.Component {
  render() {
    return <div>Hello World</div>;
  }
}

ReactDOMServer.renderToString(<MyComponent />);
```

## API

### `react-dom`

- `findDOMNode`
- `render`
- `unmountComponentAtNode`

### `react-dom/server`

- `renderToString`
- `renderToStaticMarkup`
npm package: @superhuman/zen
Description: Karma replacement that runs your tests in seconds
Latest version: 0.5.6

# Brief Overview of how Zen works

Zen is a test running that runs tests on lambda in a very parallel way. Overview of how this works when running the zen remote command:

- Code in cli.ts handles command line args and sending messages to lambda worker.
- We run the `listTests` function on aws lambda. This gets us all the test names. Test names are gotten by loading the code and all of the it(’’) blocks register the tests.
  - Tests can’t be known statically since we do thingsl like `it(`run thing ${n}, function ()` { … })
- We take all of the test names split them up into groups and run them in parallel. The actual test running happens on the lambda worker via workTests.
  - When we run the test on lambda we are running a full chrome headless browser via puppeteer.
- We gather the results and print them out.

# Publishing a new version

- Log into `npm` with an account that has publish permissions (if you don't have
  this, create one and ask Conrad): `npm login`
- Bump the version number in `package.json`
- Add a line item to `CHANGELOG.md`
- Run `yarn release-new-version`

# Uploading new Lambda Code

## Function Code

To upload new code function code to lambda you can use this script

`SECRET_ACCESS_KEY={insert secret here} ACCESS_KEY_ID={insert access here} yarn run tools:upload-lambda --env staging`

Note if you set --env production this changes the code that all of our tests use in ci. Do this only when things have been fully tested on staging and your corresponding code is merged in.

## Layer Code

For lambda files that change infrequently we have layers. The layers we use are:

- Production:

  - zen-dependencies-production
  - chromium-staging-production

- Staging
  - zen-dependencies-staging
  - chromium-staging

chromium layer is chrome build from @sparticuz/chromium releases x86 arch
zen-dependencies layer is the node dependencies like puppeteer.
Currently no script to upload these just manually use the aws ui. Password can be found in 1pass. Similar to above don't change production until things are fully tested on staging. Production is used by all of our ci.

# Developing Locally

If you want to develop locally against the Superhuman desktop repo you can:

- Run `yarn link` in this repo (you only need to do this once after downloading the repo)
- Go to the Superhuman desktop repo and run `yarn link @superhuman/zen`
- Run `yarn start` in this repo to build the zen library

- When you are done run `yarn unlink @superhuman/zen` in the desktop repo.
npm package: @supericium/pli
Description: Standard directory layout for all supericium modules.
Author: Ole Ersoy
Latest version: 0.0.1

# Supericium Project Layout Instance

The PLI (Project Layout Instance) is a javascript object model of the standard directory layout that all [Supericium](https://github.com/supericium/supericium/) modules use.  The standard layout enables users to instantly feel at home in any one of the [Supericium](https://github.com/supericium/supericium/) modules.

The PLI is inspired by the [Apache Maven Standard Directory Layout](https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html).

## Directory Descriptions

The following directories are modeled by the PLI.

### Source Directories

| Directory     | Summary                                                   |
|:--------------|:----------------------------------------------------------|
| src/main/css  | Entry level CSS module(s) are contained in this directory |
| src/main/js   | Javascript supporting dynamic demoes                      |
| src/main/html | Dynamic demonstrations                                    |
| src/test/css  | CSS test utilities                                        |
| src/test/js   | Javascript supporting CSS unit tests                      |
| src/test/html | Html pages for loading the unit tests                     |

### Target Directories

| Directory        | Summary                       |
|:-----------------|:------------------------------|
| target/main/css  | Built CSS modules             |
| target/main/js   | Built javascript              |
| target/main/html | Built dynamic demo html pages |
| target/test/css  | Built test CSS utilities      |
| target/test/js   | Built test Javascript         |
| target/test/html | Built test html               |

## Extension

More directories can easily be added, and will naturally fit with the build methodology.  For example:

| Directory            | Summary        |
|:---------------------|:---------------|
| src/main/coffescript | Coffescript    |
| src/main/jade        | Jade templates |
npm package: @superinbox/mcp-server
Description: SuperInbox MCP server (stdio)
Latest version: 0.1.11

# @superinbox/mcp-server

SuperInbox MCP server over stdio, published as an npm executable package.

Project: [guchang/superinbox](https://github.com/guchang/superinbox)

## Requirements

- Node.js >= 18
- A running SuperInbox backend (`http://127.0.0.1:3000` by default)
- A valid SuperInbox API key

## Quick Start

Use `npx` directly from your MCP client config:

```json
{
  "mcpServers": {
    "superinbox": {
      "command": "npx",
      "args": ["-y", "@superinbox/mcp-server"],
      "env": {
        "SUPERINBOX_BASE_URL": "http://127.0.0.1:3000",
        "SUPERINBOX_API_KEY": "sk_xxx"
      }
    }
  }
}
```

For deterministic environments, pin to an exact version:

```json
{
  "mcpServers": {
    "superinbox": {
      "command": "npx",
      "args": ["-y", "@superinbox/mcp-server@<version>"],
      "env": {
        "SUPERINBOX_BASE_URL": "http://127.0.0.1:3000",
        "SUPERINBOX_API_KEY": "sk_xxx"
      }
    }
  }
}
```

## Runtime Environment Variables

- `SUPERINBOX_BASE_URL`: SuperInbox backend base URL (default: `http://127.0.0.1:3000`)
- `SUPERINBOX_API_KEY`: SuperInbox API key (required)

## Exposed MCP Tools

- `inbox.create` / `inbox_create`: create a new inbox item (text/url), or upload local files via `filePath`/`filePaths`/`fileBase64`
- `inbox.list` / `inbox_list`: list items with filters and pagination
- `inbox.search` / `inbox_search`: search items by keyword
- `inbox.get` / `inbox_get`: fetch one item by `id`
- `inbox.update` / `inbox_update`: update item `content` and/or `category` by `id`
- `inbox.delete` / `inbox_delete`: delete one item by `id`
- `category.list` / `category_list`: list categories
- `category.create` / `category_create`: create category with `key` and `name`
- `category.update` / `category_update`: rename category by `id`
- `category.delete` / `category_delete`: delete category by `id` (records are migrated to `trash`)

## Troubleshooting

- `SUPERINBOX_API_KEY is not set`
  - Add `SUPERINBOX_API_KEY` in MCP server `env`.
- `HTTP 401` or `HTTP 403`
  - API key is invalid, expired, or lacks permission.
- `ECONNREFUSED` or timeout
  - Ensure backend is running and `SUPERINBOX_BASE_URL` is reachable from the MCP client host.
- `File not found: ...`
  - When using `filePath`/`filePaths` (or legacy `type="file"` + `content="/path/to/file"`), the file must exist on the same machine where the MCP server process is running. Prefer absolute paths.
- `npx: command not found`
  - Install Node.js 18+ and ensure Node/npm are in `PATH`.

## Local Development

```bash
npm install
npm run build
SUPERINBOX_BASE_URL=http://127.0.0.1:3000 SUPERINBOX_API_KEY=sk_xxx node dist/index.js
```

## Maintainer: Publish

```bash
npm login
npm publish --access public
```