open-index/open-npm huggingface dataset:
npm package: @sanity/textmate-groq
Description: TextMate grammar for GROQ query language
Latest version: 1.1.2

# @sanity/textmate-groq

TextMate grammar for [GROQ](https://www.sanity.io/docs/groq) syntax highlighting.

Used by VS Code extensions, [Shiki](https://shiki.style/) (static syntax highlighting for documentation), Sublime Text, and [GitHub/Linguist](https://github.com/github-linguist/linguist).

## Install

```bash
npm install @sanity/textmate-groq
```

## Usage with Shiki

```ts
import {createHighlighterCore} from 'shiki/core'
import {createJavaScriptRegExpEngine} from 'shiki/engine/javascript'
import groqGrammar from '@sanity/textmate-groq'

const highlighter = await createHighlighterCore({
  themes: [import('shiki/themes/github-dark.mjs')],
  langs: [{...groqGrammar, name: 'groq'}],
  engine: createJavaScriptRegExpEngine(),
})

const html = highlighter.codeToHtml('*[_type == "post"]{title}', {
  lang: 'groq',
  theme: 'github-dark',
})
```

## JavaScript/TypeScript injection

An injection grammar for highlighting GROQ inside JS/TS template literals is included:

```ts
// All of these patterns are recognized:
const query1 = groq`*[_type == "post"]`
const query2 = /* groq */ `*[_type == "post"]`
const query3 = defineQuery(`*[_type == "post"]`)
```

## Markdown fenced code block injection

An injection grammar for highlighting ` ```groq ` fenced code blocks in VS Code's markdown preview:

The injection grammar is at `injections/markdown.tmLanguage.json`.

## Usage with VS Code extensions

In your extension's `package.json`:

```json
{
  "contributes": {
    "languages": [{
      "id": "groq",
      "extensions": [".groq"],
      "aliases": ["GROQ"]
    }],
    "grammars": [
      {
        "language": "groq",
        "scopeName": "source.groq",
        "path": "./node_modules/@sanity/textmate-groq/syntaxes/groq.tmLanguage.json"
      },
      {
        "scopeName": "groq-injection.js",
        "path": "./node_modules/@sanity/textmate-groq/injections/javascript.tmLanguage.json",
        "injectTo": ["source.js", "source.ts", "source.tsx", "source.jsx"]
      },
      {
        "scopeName": "groq-injection.markdown",
        "path": "./node_modules/@sanity/textmate-groq/injections/markdown.tmLanguage.json",
        "injectTo": ["text.html.markdown"]
      }
    ]
  }
}
```

## Exports

- `@sanity/textmate-groq` - the main grammar (`syntaxes/groq.tmLanguage.json`)
- `@sanity/textmate-groq/injections/javascript` - JS/TS injection grammar
- `@sanity/textmate-groq/injections/markdown` - Markdown fenced code block injection

## License

MIT
npm package: @sanity/timed-out
Description: Emit `ETIMEDOUT` or `ESOCKETTIMEDOUT` when ClientRequest is hanged
Author: Vsevolod Strukchinsky
Latest version: 4.0.2

# timed-out [![Build Status](https://travis-ci.org/floatdrop/timed-out.svg?branch=master)](https://travis-ci.org/floatdrop/timed-out)

> Timeout HTTP/HTTPS requests

Emit Error object with `code` property equal `ETIMEDOUT` or `ESOCKETTIMEDOUT` when ClientRequest is hanged.

## Usage

```js
var get = require('http').get;
var timeout = require('timed-out');

var req = get('http://www.google.ru');
timeout(req, 2000); // Set 2 seconds limit
```

### API

#### timedout(request, time)

##### request

*Required*  
Type: [`ClientRequest`](http://nodejs.org/api/http.html#http_class_http_clientrequest)

The request to watch on.

##### time

*Required*  
Type: `number` or `object`

Time in milliseconds to wait for `connect` event on socket and also time to wait on inactive socket.

Or you can pass Object with following fields:

- `connect` - time to wait for connection
- `socket`  - time to wait for activity on socket

## License

MIT © [Vsevolod Strukchinsky](floatdrop@gmail.com)
npm package: @sanity/tsconfig
Description: Shared tsconfig.json presets following best practices at Sanity.io
Author: Sanity.io
Latest version: 2.1.0

# @sanity/tsconfig

Shared tsconfig.json presets following best practices at Sanity.io

## Installation

Add the package to your `"devDependencies"`:

```sh
npm install --save-dev @sanity/tsconfig
# or
pnpm add --save-dev @sanity/tsconfig
# or
yarn add --dev @sanity/tsconfig
```

## Usage

Choose one of the presets as your base:

- [`@sanity/tsconfig/recommended`]
- [`@sanity/tsconfig/strict`]
- [`@sanity/tsconfig/strictest`]

You can optionally combine your base with [`@sanity/tsconfig/isolated-declarations`] if you're using build tools (like `rolldown` or `tsdown`) that can generate `.d.ts` files significantly faster when TypeScript is constrained with `"isolatedDeclarations": true`.

### Recommended <kbd><a href="./recommended.tsconfig.json">tsconfig.json</a></kbd>

Add to your `tsconfig.json`:

```json
{
  "extends": "@sanity/tsconfig/recommended"
}
```

### Strict <kbd><a href="./strict.tsconfig.json">tsconfig.json</a></kbd>

Add to your `tsconfig.json`:

```json
{
  "extends": "@sanity/tsconfig/strict"
}
```

### Strictest <kbd><a href="./strictest.tsconfig.json">tsconfig.json</a></kbd>

Add to your `tsconfig.json`:

```json
{
  "extends": "@sanity/tsconfig/strictest"
}
```

### Isolated Declarations <kbd><a href="./isolated-declarations.tsconfig.json">tsconfig.json</a></kbd>

Extend the `isolated-declarations.json` preset in addition to your base.
If your `tsconfig.json` previously looked like this:

```json
{
  "extends": "@sanity/tsconfig/strict"
}
```

Then change `extends` to an array and `isolated-declarations` to the end:

```json
{
  "extends": ["@sanity/tsconfig/strict", "@sanity/tsconfig/isolated-declarations"]
}
```

[`@sanity/tsconfig/recommended`]: #recommended-tsconfigjson
[`@sanity/tsconfig/strict`]: #strict
[`@sanity/tsconfig/strictest`]: #strictest
[`@sanity/tsconfig/isolated-declarations`]: #isolated-declarations
npm package: @sanity/tsdoc
Description: Generate API reference docs from TypeScript projects and store in a Sanity-friendly JSON format. Render a static frontend, or as React components.
Author: Sanity.io
Latest version: 4.0.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# @sanity/tsdoc

Generate API reference docs from TypeScript projects and store in a Sanity-friendly JSON format. Render a static frontend, or as React components.

```sh
npm install @sanity/tsdoc
```

[![](https://img.shields.io/npm/v/@sanity/tsdoc?style=flat)](https://www.npmjs.com/package/@sanity/tsdoc)
[![](https://img.shields.io/npm/l/@sanity/tsdoc.svg?style=flat)](LICENSE)

## How to Release

The only thing you should need to do is to merge into the `main` branch.
The release actions after merging should do the rest.

Make sure that you also don't only have chore commit messages

**Note: If you squash and merge make sure that your PR title is named according to the semantic messages so that the sematic release can happen automatically. Otherwise you'll have to amment the commit message to an appropriate one**

https://github.com/semantic-release/semantic-release

## License

[MIT](https://github.com/sanity-io/tsdoc/blob/main/LICENSE) © [Sanity.io](https://www.sanity.io/)
npm package: @sanity/tsdoc-to-portable-text
Description: _Work in progress._
Author: Sanity.io
Latest version: 0.4.3

# @sanity/tsdoc-to-portable-text

_Work in progress._

## Installation

```sh
npm i @sanity/tsdoc-to-portable-text
```

## Using the CLI

```sh
# Extract to etc/<version>.json using `tsdoc-to-portable-text etl` command
tsdoc-to-portable-text etl dist/index.d.ts --outDir etc/ --tsconfig tsconfig.dist.json
```

## Using the Node.js API

```ts
import {extract, load, transform} from '@sanity/tsdoc-to-portable-text'

// Path to a package with a package.json file
const packagePath = __dirname

const result = await extract('dist/index.d.ts', {
  packagePath,
  tsconfigPath: 'tsconfig.dist.json',
})

const docs = transform(result, {package: {scope: null, name: 'mylib', version: '1.0.0'}})

await load(docs, {fs: {path: path.resolve(packagePath, 'etc/1.0.0.json')}})
```
npm package: @sanity/tsdown-config
Description: Shared configuration for tsdown
Author: Sanity.io
Latest version: 0.5.8

Shared config for tsdown

```sh
pnpm add --save-dev @sanity/tsdown-config tsdown
```

Create a `tsdown.config.ts` file with:

```ts
import {defineConfig} from '@sanity/tsdown-config'

export default defineConfig({tsconfig: 'tsconfig.dist.json'})
```
npm package: @sanity/ui
Description: The Sanity UI components.
Author: Sanity.io
Latest version: 3.1.14

# @sanity/ui

The Sanity UI components.

```sh
npm install @sanity/ui

# Install peer dependencies
npm install react react-dom styled-components
```

[![npm version](https://img.shields.io/npm/v/@sanity/ui.svg?style=flat-square)](https://www.npmjs.com/package/@sanity/ui)

## Usage

```jsx
import {Button, ThemeProvider} from '@sanity/ui'
import {buildTheme} from '@sanity/ui/theme'
import {createRoot} from 'react-dom/client'

const root = createRoot(document.getElementById('root'))
const theme = buildTheme()

root.render(
  <ThemeProvider theme={theme}>
    <Button text="Hello, world" />
  </ThemeProvider>,
)
```

## License

MIT-licensed. See LICENSE.
npm package: @sanity/ui-workshop-plugin-sanity
Description: Wrap your UI workshop in the Sanity context to test your Sanity-connected components.
Author: Sanity.io
Latest version: 2.0.1

# @sanity/ui-workshop-plugin-sanity

Wrap your UI workshop in the Sanity context to test your Sanity-connected components.

```sh
# Install `@sanity/ui-workshop-plugin-sanity` as dev dependency
npm install @sanity/ui-workshop-plugin-sanity -D

# Install peer dependencies
npm install @sanity/icons @sanity/ui react react-dom styled-components
```

[![npm version](https://img.shields.io/npm/v/@sanity/ui-workshop-plugin-sanity.svg?style=flat-square)](https://www.npmjs.com/package/@sanity/ui-workshop-plugin-sanity)

## Basic usage

Add the plugin to your `workshop.config.ts` (or .js) in the root of your project:

```ts
import {defineConfig} from '@sanity/ui-workshop'
import {sanity} from '@sanity/ui-workshop-plugin-sanity'
import sanityConfig from './sanity.config'

export default defineConfig({
  title: 'My UI Workshop',
  plugins: [sanity({config: sanityConfig})],
})
```

## License

[MIT](LICENSE)
npm package: @sanity/uuid
Description: Simple generation of sanity document IDs
Author: Sanity.io
Latest version: 3.0.2

# @sanity/uuid

Generate a valid Sanity document ID

## Installation

```sh
$ npm install @sanity/uuid
// or
$ yarn add @sanity/uuid
```

## Usage

```js
import {uuid} from '@sanity/uuid'

const id = uuid()
console.log(id)
//=> 76dc5edf-9c43-4bab-a62d-4a2cad650053
```

## License

MIT © [Sanity.io](https://www.sanity.io/)
npm package: @sanity/vercel-protection-bypass
Description: [![npm stat](https://img.shields.io/npm/dm/@sanity/vercel-protection-bypass.svg?style=flat-square)](https://npm-stat.com/charts.html?package=@sanity/vercel-protection-bypass) [![npm version](https://img.shields.io/npm/v/@sanity/vercel-protection-bypass.sv
Author: Sanity.io
Latest version: 5.0.6

# @sanity/vercel-protection-bypass

[![npm stat](https://img.shields.io/npm/dm/@sanity/vercel-protection-bypass.svg?style=flat-square)](https://npm-stat.com/charts.html?package=@sanity/vercel-protection-bypass)
[![npm version](https://img.shields.io/npm/v/@sanity/vercel-protection-bypass.svg?style=flat-square)](https://www.npmjs.com/package/@sanity/vercel-protection-bypass)

> [!IMPORTANT]  
> This plugin requires React 19.2 or later, and Sanity Studio v4.

```sh
npm install @sanity/vercel-protection-bypass
```

This package is used together with [`sanity/presentation`] to configure it to work with Vercel's [Deployment Protection](https://vercel.com/docs/security/deployment-protection) feature.
The tool is only needed for setup, once it's configured you can safely uninstall it.

Add the tool your `sanity.config.ts`:

```ts
// ./sanity.config.ts
import {vercelProtectionBypassTool} from '@sanity/vercel-protection-bypass'
import {defineConfig} from 'sanity'
import {presentationTool} from 'sanity/presentation'

export default defineConfig({
  // ... other options
  plugins: [
    // ... other plugins
    presentationTool({
      previewUrl: {
        // @TODO change to the URL of the application, or `location.origin` if it's an embedded Studio
        origin: 'http://localhost:3000',
        previewMode: {
          enable: '/api/draft',
        },
      },
    }),
    vercelProtectionBypassTool(),
  ],
})
```

You should see a new `Vercel Protection Bypass` tab in the Studio's settings. Click it and follow the instructions to set up the tool.

[`sanity/presentation`]: https://www.sanity.io/docs/visual-editing/configuring-the-presentation-tool
npm package: @sanity/visual-editing-csm
Description: > [!WARNING]   > This package is not meant to be used directly, it's an internal dependency. Using it in production is at your own risk.
Author: Sanity.io
Latest version: 3.0.6

# @sanity/visual-editing-csm

> [!WARNING]  
> This package is not meant to be used directly, it's an internal dependency. Using it in production is at your own risk.
npm package: @sanity/visual-editing-types
Description: > [!WARNING]   > Don't use this package directly, it's an internal package used by `@sanity/presentation-comlink` & `@sanity/visual-editing-csm`
Author: Sanity.io
Latest version: 2.0.5

# @sanity/visual-editing-types

> [!WARNING]  
> Don't use this package directly, it's an internal package used by `@sanity/presentation-comlink` & `@sanity/visual-editing-csm`
npm package: @saniul/opentelemetry-instrumentation-ws
Description: Adds opentelemetry tracing instrumentation for the `ws` library. Traces socket opens, closes, sends, and optionally messages for the `WebSocket` constructor, and traces upgrades that happen on `http.Server`, `https.Server`, and `WebSocket.Server`.
Latest version: 0.5.0-fork1

# opentelemetry-instrumentation-ws

Adds opentelemetry tracing instrumentation for the `ws` library. Traces socket opens, closes, sends, and optionally messages for the `WebSocket` constructor, and traces upgrades that happen on `http.Server`, `https.Server`, and `WebSocket.Server`.

## Installation

Install the package with

```
npm install opentelemetry-instrumentation-ws
```

or

```
yarn add opentelemetry-instrumentation-ws
```

## Usage

You must register the intstrumentation using the OpenTelemetry Node SDK, and you must take care to do this as soon as possible so the patches to the `ws` library are made before your app's code requires the library.

```typescript
import { WSInstrumentation } from "opentelemetry-instrumentation-ws";

import { registerInstrumentations } from '@opentelemetry/instrumentation';

registerInstrumentations({
  tracerProvider,
  instrumentations: [
    new WSInstrumentation({
      // see below for configuration options
    })
  ]
});
```

## Config

The `ws` instrumentation has few options available to choose from. You can set the following:

| Options             | Type                                     | Description                                                                                                    |
| ------------------- | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| `sendSpans`         | boolean                                  | should the tracing library add spans for each sent message. Default: false                                     |
| `messageEvents`     | boolean                                  | should the tracing library add span events for each incoming message. Default: false                           |
| `sendHook`          | (span: Span, hookInfo: HookInfo) => void | hook for adding custom attributes to the ws send span when a websocket sends a message                         |
| `closeHook`         | (span: Span, hookInfo: HookInfo) => void | hook for adding custom attributes to the ws close span when a websocket is imperatively closed                 |
| `handleUpgradeHook` | (span: Span, hookInfo: HookInfo) => void | hook for adding custom attributes to the ws.Server handleUpgrade span when a socket is opened against a server |
npm package: @saniyavinod/dummy_package1
Description: dummy
Author: saniyavinod
Latest version: 0.2.0

# dummy_package

dummy

## Installation

```sh
npm install dummy_package
```

## Usage


```js
import { multiply } from 'dummy_package';

// ...

const result = await multiply(3, 7);
```


## Contributing

See the [contributing guide](CONTRIBUTING.md) to learn how to contribute to the repository and the development workflow.

## License

MIT

---

Made with [create-react-native-library](https://github.com/callstack/react-native-builder-bob)
npm package: @sanjai-plugin/devcheck
Description: Detect Android Developer Options ON/OFF for Capacitor
Author: wellteam
Latest version: 0.0.6

# devcheck

its just developer options verify plugin

## Install

To use npm

```bash
npm install devcheck
````

To use yarn

```bash
yarn add devcheck
```

Sync native files

```bash
npx cap sync
```

## API

<docgen-index>

* [`isDevOptionsEnabled()`](#isdevoptionsenabled)
* [`echo(...)`](#echo)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### isDevOptionsEnabled()

```typescript
isDevOptionsEnabled() => Promise<{ enabled: boolean; }>
```

Checks whether Android Developer Options are ON or OFF.
Returns a Promise with `{ enabled: boolean }`

**Returns:** <code>Promise&lt;{ enabled: boolean; }&gt;</code>

--------------------


### echo(...)

```typescript
echo(options: { value: string; }) => Promise<{ value: string; }>
```

Optional: Echo method for testing

| Param         | Type                            |
| ------------- | ------------------------------- |
| **`options`** | <code>{ value: string; }</code> |

**Returns:** <code>Promise&lt;{ value: string; }&gt;</code>

--------------------

</docgen-api>
npm package: @sanjai-plugin/myplugin
Description: demo purpose
Author: sanjai
Latest version: 0.0.1

# myplugin

demo purpose

## Install

```bash
npm install myplugin
npx cap sync
```

## API

<docgen-index>

* [`validateField(...)`](#validatefield)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### validateField(...)

```typescript
validateField(options: { value: string; rule: string; minLength?: number; }) => Promise<{ valid: boolean; message: string; }>
```

| Param         | Type                                                              |
| ------------- | ----------------------------------------------------------------- |
| **`options`** | <code>{ value: string; rule: string; minLength?: number; }</code> |

**Returns:** <code>Promise&lt;{ valid: boolean; message: string; }&gt;</code>

--------------------

</docgen-api>
npm package: @sanjanad-2109/lowcoder-comp-my-plugin
Description: ## Prerequisites Before you start, ensure you have a running Lowcoder installation. Alternatively, you can use it online at [https://app.lowcoder.cloud](https://app.lowcoder.cloud).
Latest version: 0.0.4

# Using Lowcoder Component Plugin

## Prerequisites
Before you start, ensure you have a running Lowcoder installation. Alternatively, you can use it online at [https://app.lowcoder.cloud](https://app.lowcoder.cloud).

## Steps to Use the Plugin
1. **Open the App Editor**: Navigate to the App Editor within your Lowcoder application.

<p align="center">
  <img src="https://raw.githubusercontent.com/lowcoder-org/lowcoder-media-assets/main/images/App%20Editor%20%7C%20Main%20Screeen%20clean.png" alt="Lowcoder App Editor">
</p>

1. **Access Components Panel**: In the App Editor, locate the right panel where components are listed.

2. **Switch to Extensions**: Find and switch on the "Extensions" toggle. This option allows you to add additional components to your project.

<p align="center">
  <img src="https://raw.githubusercontent.com/lowcoder-org/lowcoder-media-assets/main/images/App%20Editor%20%7C%20Import%20Component%20Plugin%201.png" alt="Lowcoder App Editor">
</p>

3. **Load the Plugin**: Here you have the option to load a Lowcoder Component Plugin from NPM. For example, to load the "hill charts" plugin, type `lowcoder-comp-hillcharts` in the provided field.

<p align="center">
  <img src="https://raw.githubusercontent.com/lowcoder-org/lowcoder-media-assets/main/images/App%20Editor%20%7C%20Import%20Component%20Plugin%202.png" alt="Lowcoder App Editor">
</p>

4. **Start Using the Plugin**: After loading the plugin, it will be available for use within your Lowcoder project. You can now integrate and customize the component as per your application's needs.

<p align="center">
  <img src="https://raw.githubusercontent.com/lowcoder-org/lowcoder-media-assets/main/images/App%20Editor%20%7C%20Import%20Component%20Plugin%203.png" alt="Lowcoder App Editor">
</p>

<p align="center">
  <img src="https://raw.githubusercontent.com/lowcoder-org/lowcoder-media-assets/main/images/App%20Editor%20%7C%20Import%20Component%20Plugin%204.png" alt="Lowcoder App Editor">
</p>