open-index/open-npm huggingface dataset:
npm package: @knowitsolutions/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 3.2.0-3

# @knowitsolutions/react-scripts

This package is a fork of [Create React App](https://github.com/facebookincubator/create-react-app) (specifically the
`react-scripts` package). It's intended to be used in conjuction with `create-react-app` like so:

```sh
yarn create react-app my-app --scripts-version=@knowitsolutions/react-scripts

# start your app development like you normally would with `create-react-app`
cd my-app
yarn start
```

The setup of this fork has been modeled after another react-scripts fork: [backpack-react-scripts](https://github.com/Skyscanner/backpack-react-scripts)

## What is different in our fork?

- [source-map-loader](https://github.com/webpack-contrib/source-map-loader) added to webpack configuration.
- Source maps enabled by default for dependecies.
- Allow more jest confiuration overrides: `setupTestFrameworkScriptFile`, `testMatch`.

## Releasing a new version of `@knowitsolutions/react-scripts`

1. To publish a new version of `@knowitsolutions/react-scripts`, run the following command:

   ```
   npm run publish prerelease
   ```

   - If you want to be extra careful, you can publish a prerelease by running this instead:

   ```
   npm run publish --canary
   ```

1. Update the [CHANGELOG.md](./CHANGELOG.md) with the new version, taking care to follow the format of previous releases.

## Keeping this fork updated

We wish to keep this fork updated with the upstream repo to benefit from the ongoing open source development
of `create-react-app`. To keep this fork up to date, please follow the steps below:

1. Ensure `master` is in sync with `upstream/master`:

   ```sh
   git checkout master
   git remote add upstream git@github.com:facebook/create-react-app.git
   git fetch upstream
   git reset --hard upstream/master
   git push --force-with-lease
   ```

1. Rebase `fork` on top of a **tagged release** on `master`:

   ```sh
   git checkout fork
   git rebase <commit>
   ```

   > **Note:** `<commit>` should be the SHA-1 of the latest upstream release - _not_ just the latest i.e. `upstream/master`

1. Pair with someone else to fix any conflicts and cross examine changes in upstream with changes in our fork.

   > This is the most time consuming part. Take care to make sure you are not regressing any functionality that we have added in our fork.

1. Re-name your local, rebased `fork` branch to something else and push it to origin. This will ensure it runs through CI and you can verify your changes.

   ```sh
   git branch -m <branch>
   git push origin <branch>
   ```

1. Finally, when we are confident that the rebase has been successful, re-name your branch back to `fork` and push it to origin:

   ```sh
   git branch -m fork
   git push --force-with-lease
   ```
npm package: @knowledge-kit/mcp-server
Description: MCP server for Knowledge Base Self-Hosting Kit integration
Author: 2dogsandanerd
Latest version: 1.1.0

# Knowledge Base Self-Hosting Kit MCP Server

A small MCP server (`knowledge-kit-mcp`) that lets OpenClaw, Smithery, or other MCP-aware agents query the same knowledge base you run locally.

## Quick start

1. Start the Knowledge Base Self-Hosting Kit backend + frontend (`docker compose up -d`).
2. Run the MCP server close to the agent:
   ```bash
   openclaw mcp add --transport stdio knowledge-kit npx -y @knowledge-kit/mcp-server
   ```
   This installs `knowledge-kit-mcp` from npm and wires MCP to your agent.
3. The agent now exposes two tools: `query_knowledge` and `list_collections`.

## Configuration

| Env var | Purpose | Default |
|---------|---------|---------|
| `KNOWLEDGE_BASE_API_URL` | HTTP URL of the running kit backend | `http://localhost:8080` |
| `KNOWLEDGE_BASE_TIMEOUT` | Request timeout in milliseconds (used for slow local LLMs) | `120000` |
| `LOG_LEVEL` | Logging level for debugging | `INFO` |

All values can also be edited from the frontend’s **Agent Configuration** tab (the UI calls `/api/v1/config`).

## Running locally

```bash
cd mcp-server
npm install
npm run build
npm start                # CLI: knowledge-kit-mcp -> build/cli.js
npm run dev              # Development mode (ts-node)
npm run start:http        # HTTP + SSE transport for web-based agents
```

## MCP tooling

- `query_knowledge(query, collections?, k?, use_reranker?)` returns LLM answers plus citations.
- `list_collections()` shows the collection names that are already ingested.

The server card (`.well-known/mcp/server-card.json`) is already configured for shared schema discovery.