open-index/open-npm huggingface dataset:
npm package: @services-maxiphy/maxitector
Description: This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
Latest version: 0.1.1

# React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

- [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/README.md) uses [Babel](https://babeljs.io/) for Fast Refresh
- [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc) uses [SWC](https://swc.rs/) for Fast Refresh

## Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type aware lint rules:

- Configure the top-level `parserOptions` property like this:

```js
export default tseslint.config({
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})
```

- Replace `tseslint.configs.recommended` to `tseslint.configs.recommendedTypeChecked` or `tseslint.configs.strictTypeChecked`
- Optionally add `...tseslint.configs.stylisticTypeChecked`
- Install [eslint-plugin-react](https://github.com/jsx-eslint/eslint-plugin-react) and update the config:

```js
// eslint.config.js
import react from 'eslint-plugin-react'

export default tseslint.config({
  // Set the react version
  settings: { react: { version: '18.3' } },
  plugins: {
    // Add the react plugin
    react,
  },
  rules: {
    // other rules...
    // Enable its recommended rules
    ...react.configs.recommended.rules,
    ...react.configs['jsx-runtime'].rules,
  },
})
```
npm package: @servicestack/angular
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.0.0.
Latest version: 0.15.0

# Angular

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.0.0.

## Code scaffolding

Run `ng generate component component-name --project angular` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project angular`.
> Note: Don't forget to add `--project angular` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build angular` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build angular`, go to the dist folder `cd dist/angular` and run `npm publish`.

## Running unit tests

Run `ng test angular` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @servicestack/images
Description: Collection of free images and resources for Websites and Apps
Author: ServiceStack
Latest version: 1.0.0

# images

Collection of free images and resources for Websites and Apps served from GitHub's CDN.

The [heroes.js](https://github.com/ServiceStack/images/blob/master/heroes.js) module returns different URLs to 2560x1000 [/hero](https://github.com/ServiceStack/images/tree/master/hero) images ideal for usage in hero backgrounds.

> Live Example: [/heroes](https://servicestack.github.io/images/heroes)

# usage

From web page:

```html
<script src="https://servicestack.github.io/images/heroes.js" />

<script>document.write(`<img src="${heroes.random()}">`)</script>
```

From a npm-based Web App:

    $ npm install @servicestack/images

Import using ES6 modules or TypeScript:

```js
import { heroes } from "@servicestack/images";
```

### React Example

```jsx
const Hero = <img src={heroes.random()} />;
```

### Vue Example

```html
<template>
  <img :src="heroes.daily()">
</template>

<script>
import { heroes } from "@servicestack/images";

export default {
  methods: {
    heroes
  }
}
</script>
```

### dependency-free

As [heroes.js](https://github.com/ServiceStack/images/blob/master/heroes.js) doesn't have any dependencies it can also be copied and used locally:

    $ curl https://servicestack.github.io/images/heroes.js -o heroes.js

Where it can be referenced as a relative module:

```js
import heroes from "./heroes";

console.log(heroes.random());
```
npm package: @servicestack/react
Description: ServiceStack's React Component Library - A comprehensive collection of React components for building modern web applications.
Latest version: 2.0.17

# @servicestack/react

ServiceStack's React Component Library - A comprehensive collection of React components for building modern web applications.

## Features

- 🎨 **Beautiful UI Components** - Pre-styled components with Tailwind CSS
- 🔄 **Framework Agnostic Routing** - Works with React Router, Next.js, or plain HTML
- ⚡ **React 19 Compatible** - Full support for React 19 including SSR mode
- 📦 **TypeScript Support** - Fully typed components and APIs
- 🎯 **AutoQuery Integration** - Built-in components for ServiceStack AutoQuery APIs
- 🌙 **Dark Mode Support** - All components support dark mode out of the box

## Quick Start

### Installation

```bash
npm install @servicestack/react
```

### Configuration

The library supports multiple routing solutions. Choose the one that fits your project:

#### React Router (Vite, CRA, etc.)

```tsx
import { setLinkComponent } from '@servicestack/react'
import { Link } from 'react-router-dom'

setLinkComponent(Link)
```

#### Next.js

```tsx
import { setLinkComponent } from '@servicestack/react'
import Link from 'next/link'

setLinkComponent(Link)
```

#### No Router (Plain HTML)

No configuration needed! Components will automatically use standard anchor tags.

For detailed setup instructions, see [SETUP.md](./SETUP.md).

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [ESLint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) + [TypeScript](https://www.typescriptlang.com/)

For the best development experience, we recommend:
- [ES7+ React/Redux/React-Native snippets](https://marketplace.visualstudio.com/items?itemName=dsznajder.es7-react-js-snippets)
- Built-in TypeScript support in VSCode

## Customize configuration

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```sh
npm install
```

### Compile and Hot-Reload for Development

```sh
npm run dev
```

### Type-Check, Compile and Minify for Production

```sh
npm run build
```

## Examples

Check out the [examples](./examples) directory for complete setup examples:

- [React Router Setup](./examples/react-router-setup.tsx) - Vite + React + React Router
- [Next.js App Router Setup](./examples/nextjs-app-router-setup.tsx) - Next.js 13+ with App Router
- [Next.js Pages Router Setup](./examples/nextjs-pages-router-setup.tsx) - Traditional Next.js routing
- [No Router Setup](./examples/no-router-setup.tsx) - Plain React without routing

## Documentation

For comprehensive documentation, visit [docs.servicestack.net/react](https://docs.servicestack.net/react/)

## License

This project is licensed under the terms specified in the LICENSE file.
npm package: @servicestack/vue
Description: This is ServiceStack's [Vue Component Library](https://docs.servicestack.net/vue).
Latest version: 3.1.5

# @servicestack/vue

This is ServiceStack's [Vue Component Library](https://docs.servicestack.net/vue).

## Recommended IDE Setup

[VSCode](https://code.visualstudio.com/) + [Volar](https://marketplace.visualstudio.com/items?itemName=Vue.volar) (and disable Vetur) + [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin).

## Type Support for `.vue` Imports in TS

TypeScript cannot handle type information for `.vue` imports by default, so we replace the `tsc` CLI with `vue-tsc` for type checking. In editors, we need [TypeScript Vue Plugin (Volar)](https://marketplace.visualstudio.com/items?itemName=Vue.vscode-typescript-vue-plugin) to make the TypeScript language service aware of `.vue` types.

If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a [Take Over Mode](https://github.com/johnsoncodehk/volar/discussions/471#discussioncomment-1361669) that is more performant. You can enable it by the following steps:

1. Disable the built-in TypeScript Extension
    1) Run `Extensions: Show Built-in Extensions` from VSCode's command palette
    2) Find `TypeScript and JavaScript Language Features`, right click and select `Disable (Workspace)`
2. Reload the VSCode window by running `Developer: Reload Window` from the command palette.

## Customize configuration

See [Vite Configuration Reference](https://vitejs.dev/config/).

## Project Setup

```sh
npm install
```

### Compile and Hot-Reload for Development

```sh
npm run dev
```

### Type-Check, Compile and Minify for Production

```sh
npm run build
```
npm package: @servicetitan/anvil2-mcp
Description: Anvil2 MCP for ServiceTitan
Author: ServiceTitan
Latest version: 0.0.8

# Anvil2 MCP Server

MCP server for accessing ServiceTitan's Anvil2 React component documentation.

## Installation

### Cursor

[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=Anvil2&config=eyJ0eXBlIjoic3RkaW8iLCJjb21tYW5kIjoibnB4IC15IEBzZXJ2aWNldGl0YW4vYW52aWwyLW1jcEBsYXRlc3QifQ%3D%3D)

#### Manual Installation

Add the following to your Cursor settings JSON:

```json
{
  "mcpServers": {
    "Anvil2": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@servicetitan/anvil2-mcp@latest"]
    }
  }
}
```

### VS Code Installation

#### Command-line

```bash
code --add-mcp "{\"name\":\"Anvil2\",\"command\":\"npx\",\"args\":[\"-y\",\"@servicetitan/anvil2-mcp@latest\"]}"
```

#### URL Handler

You can also install by opening this link:

```
vscode:mcp/install?%7B%22name%22%3A%22Anvil2%22%2C%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22-y%22%2C%22%40servicetitan%2Fanvil2-mcp%40latest%22%5D%7D
```

## Available Tools

### `get_all_components`

Lists all available Anvil2 React components.

**Parameters**: None

**Returns**: JSON array of component names

### `get_component_by_name`

Retrieves detailed documentation for a specific Anvil2 component.

**Parameters**:

- `name` (string, required): The name of the Anvil2 component

**Returns**: Markdown-formatted documentation including design specs, usage guidelines, React implementation details, props, and examples.

### `get_full_documentation`

Retrieves documentation for all components at once.

**Parameters**: None

**Returns**: Markdown-formatted documentation containing all Anvil2 components' documentation in a single response, including design specs, usage guidelines, React implementation details, props, and examples for each component.

## Development

```bash
pnpm install
pnpm dev
```
npm package: @servicetitan/docs-anvil-uikit-contrib
Description: This package contains documentation for Frontend Community packages, published at https://docs.st.dev.
Latest version: 38.7.0

# `@servicetitan/docs-anvil-uikit-contrib`

This package contains documentation for Frontend Community packages, published at https://docs.st.dev.

<!---
## Preview changes locally

To preview changes use the local `docusaurus` project. See the `docusaurus` README for instructions.
-->

## Preview changes in situ

Use `yalc` to preview changes within the entire ServiceTitan Engineering documentation.

### Initial setup

1. Install the `yalc` package globally

```sh
$ npm i yalc -g
```

2. Build the `anvil-uikit-contrib` packages

```sh
$ cd <path-to-anvil-uikit-contrib>
$ npm run build
```

3. Run `yalc publish` in the `packages/docs` folder to publish the package documentation locally

```sh
$ cd ./packages/docs
$ yalc publish
```

4. Run `yalc add @servicetitan/docs-anvil-uikit-contrib` in the `servicetitan/docs` repo to use the locally published documents

```sh
$ cd <path-to-servicetitan/docs>
$ yalc add @servicetitan/docs-anvil-uikit-contrib
```

5. Update dependencies

```sh
$ npm i
```

6. Start Docusaurus

```sh
$ npm start
```

This opens the documentation in a browser window.

### Live updates

To see further changes without having to restart the server,

1. Run `yalc push` in the anvil-uikit-contrib `packages/docs` folder to push changes to `servicetitan/docs`

```sh
# > anvil-uikit-contrib/packages/docs
$ yalc push
```

2. Run `npm run prebuild` (or `npm run import-package-docs`) in `servicetitan/docs`

```sh
# > servicetitan/docs
$ npm run prebuild
```
npm package: @servicetitan/docs-uikit
Description: Documentation content for Uikit packages published at docs.st.dev
Latest version: 36.0.0

# `@servicetitan/docs-uikit`

This package contains documentation for Uikit packages, published at https://docs.st.dev.

## Preview changes locally

To preview changes use the local `docusaurus` project. See the `docusaurus` README for instructions.

## Preview changes in situ

Use `yalc` to preview changes within the entire ServiceTitan Engineering documentation.

### Initial setup

1. Install the `yalc` package globally

```sh
$ npm i yalc -g
```

2. Build the `uikit` packages

```sh
$ cd <path-to-uikit>
$ npm run build
```

3. Run `yalc publish` in the `packages/docs` folder to publish the package documentation locally

```sh
$ cd ./packages/docs
$ yalc publish
```

4. Run `yalc add @servicetitan/docs-uikit` in the `servicetitan/docs` repo to use the locally published documents

```sh
$ cd <path-to-servicetitan/docs>
$ yalc add @servicetitan/docs-uikit
```

5. Update dependencies

```sh
$ npm i
```

6. Start Docusaurus

```sh
$ npm start
```

This opens the documentation in a browser window.

### Live updates

To see further changes without having to restart the server,

1. Run `yalc push` in the uikit `packages/docs` folder to push changes to `servicetitan/docs`

```sh
# > uikit/packages/docs
$ yalc push
```

2. Run `npm run prebuild` (or `npm run import-package-docs`) in `servicetitan/docs`

```sh
# > servicetitan/docs
$ npm run prebuild
```
npm package: @servicetitan/hammer-react
Description: <h1 align="center">   Hammer React Library </h1>
Latest version: 1.42.1

<h1 align="center">
  Hammer React Library
</h1>

Hammer React contains flexible, customizable, reusable components and utilities for building complex UIs and layered design systems.

## Hammer and Anvil2 Note

In this monorepo, there are both Hammer and Anvil2 packages. Hammer (e.g. `@servicetitan/hammer-react`), is the base library that the Anvil team maintains and `@servicetitan/anvil2` builds on top of.

Anvil2 is more opinionated and ServiceTitan-specific, and can also include more complex components and customizations of Hammer.

Much of the source code for Anvil2 components (`packages/anvil2`) actually exists in this package. When releasing updates, making changes in Hammer will automatically propagate to Anvil2, as long as the component/function/type is exported from the `packages/anvil2` package as well.

# Getting Started

## Installation

We recommend installing Hammer React by running the following `npm` command (or the equivalent `yarn`/`pnpm` command) in your project folder:

```
npm install @servicetitan/hammer-react
```

## Usage

### Components

Components can be imported as named exports from the package root:

```tsx
import { Button, Icon } from "@servicetitan/hammer-react";
```

### Icons

> To learn more about Hammer Icons, head to [`packages/hammer-icon`](../hammer-icon/README.md).

Hammer icons are expected to be used with the [SVGR](https://github.com/gregberge/svgr) library, which will import SVGs as React components. SVGR is already included in the build process for this package.

Importing and using an icon:

```tsx
import { Button, Icon } from "@servicetitan/hammer-react";

import Warning from "@servicetitan/hammer-icon/mdi/round/warning.svg";
import Star from "@servicetitan/hammer-icon/mdi/round/star.svg";
import LocalSettings from "@servicetitan/hammer-icon/mdi/round/local_settings.svg";

export const Example = () => (
  <>
    <Icon svg={Warning} size="large" />
    <Button icon={Star} aria-label="Favorite" />
    <Button icon={LocalSettings}>Settings</Button>
  </>
);
```

# Contributing

We welcome contributions of all kinds from design to code!

Please reach out to our team in [#ask-designsystem](https://servicetitan.enterprise.slack.com/archives/CBSRGHTRS) if you would like to make a contribution.

Check out the [root-level Contributing docs](../../README.md#contributing) for more details on making changes to this package.