open-index/open-npm huggingface dataset:
npm package: @segment/mysql-query-validator
Description: This is just a simple wrapper over [this Golang executable](https://github.com/xwb1989/sqlparser) to validate SQL queries.
Latest version: 1.1.0

# mysql-query-validator

This is just a simple wrapper over [this Golang executable](https://github.com/xwb1989/sqlparser) to validate SQL queries.

## Installation

```bash
yarn add mysql-query-validator
```

## Example

```js
import { validate } from 'mysql-query-validator'

try {
  validate(`
    create table test (
      id varchar(20) not null,
      created_at datetime(6),
      slug varbinary(255),
      enabled tinyint(1),
      labels json // missing comma
      url blob
    )
  `)
} catch (err) {
  console.error(err.message) // syntax error at position N near 'url'
}
```
npm package: @segment/public-api-sdk-typescript
Description: NodeJS client for @segment/public-api-sdk-typescript
Latest version: 73.0.0-b18814

# Segment Public API TypeScript SDK

:warning: This SDK is currently released as [Public Beta](https://segment.com/legal/first-access-beta-preview/). Its use in critical systems is discouraged, but [feedback is welcome](#contributing).

## Overview

The Segment Public API helps you manage your Segment Workspaces and its resources. You can use the API to perform CRUD (create, read, update, delete) operations at no extra charge. This includes working with resources such as Sources, Destinations, Warehouses, Tracking Plans, and the Segment Destinations and Sources Catalogs. The full documentation is available at [https://docs.segmentapis.com](https://docs.segmentapis.com).

All endpoints in the API follow REST conventions and use standard HTTP methods. Different URL endpoints represent different resources in a Workspace.

See the next sections for more information on how to use the Segment Public API TypeScript SDK.

Latest API and SDK version: 73.0.0

## Installation

This SDK is published as an [NPM package](https://npmjs.org). To install it, use:

```
npm i @segment/public-api-sdk-typescript
```

Or, if you're using yarn:

```
yarn add @segment/public-api-sdk-typescript
```

To build and compile the SDK from source, clone this repository and use:

```
yarn install
yarn build
```

This will output the compiled JavaScript files in the `dist/` directory.

You are now ready to start making calls to Public API!

## Example

```typescript
import * as PublicAPI from '@segment/public-api-sdk-typescript';

const TOKEN = '...'; // fetch your token from a secure location

const { workspaces } = PublicAPI.configureApis(TOKEN);
// To access the EU endpoint, use `const { workspaces } = PublicAPI.configureEuApis(TOKEN)`

PublicAPI.unwrap(workspaces.getWorkspace())
    .then((result) => {
        console.log(JSON.stringify(result));
    })
    .catch(console.error);
```

## Contributing

The contents of this repository are automatically generated, so we can't take contributions from external developers. If you have any issues with this SDK, please raise an issue or reach out to friends@segment.com instead of opening a pull request. Pull requests will not be reviewed.
npm package: @segment/react-ui-library
Description: > Presentational React Components with a coherent API for developers
Latest version: 9.0.3

# React UI library for Segment
> Presentational React Components with a coherent API for developers

* Powerful component API
* Dedicated UI engineering workflow
* Documentation with React Storybook
* Powerful prototyping tool

## Install

```
$ yarn add @segment/react-ui-library
```

## React Storybook and Documentation

React Storybook will be used as a reference and documentation for most components.

```
yarn run storybook
```

Open [http://localhost:9009/](http://localhost:9009/) to see the Storybook

## Usage

Using the `react-ui-library` should be fairly straightforward.
Install and then import whatever components you need:

```jsx
import React from 'react'
import ReactDOM from 'react-dom'
import {
  Button
} from '@segment/react-ui-library'

ReactDOM.render(<Button primary>I am using the UI Library!</Button>, document.getElementById('root'))
```

Read the Storybook for more documentation.

## Releasing a new version

Run `make release` on the `master` branch and follow the instructions. Avoid breaking changes in minor and patch releases.

## Creating new components

1. Create a new component in `/src/components/Comp.js`
2. Create a new test for your component `/src/components/Comp.test.js`
3. Create a new story in `/src/stories/Comp.js` with documentation and examples
npm package: @segment/snippet
Description: Templating methods for rendering the analytics.js snippet.
Author: Segment.io
Latest version: 5.2.1

# @segment/snippet

Render the analytics.js snippet.

The recommended way to use analytics.js is to follow the [analytics.js quickstart guide](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/). If you absolutely need to generate a snippet dynamically, this is an alternate solution. Note that when using this in-browser, the global `analytics` object will not be defined until the snippet is rendered and executed.

For information on browser support, see: https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/supported-browsers/

## Installation
```sh
# npm
npm install @segment/snippet

# yarn
yarn add @segment/snippet

# pnpm
pnpm add @segment/snippet
```
## Example

```js
const snippet = require('@segment/snippet');

const contents = snippet.max({
  host: 'cdn.segment.com',
  apiKey: '03fwkuu3',
  page: {
    category: 'Docs',
    name: 'Integrations',
    properties: {
      foo: 'bar'
    }
  }
});
```

## API

### snippet.max(options)

Returns the maxified version of the analytics.js snippet given a set of `options`:

* `host`: the domain name where the analytics.js script is hosted.
* `useHostForBundles`: If set to `true`, the snippet will include the `_cdn` property to tell analytics.js where to fetch bundles from.
* `apiKey`: the `apiKey` to load in the snippet.
* `page`: the options to pass to `analytics.page`. if `page` is `false`, then the `page()` call will be omitted.
* `load`: If object, these are the settings passed as the second argument to analytics.load. This can be useful if you want to override Segment.io integration behavior, or if you want dynamically control which integraions load on the client-side for things like GDPR. If set to `false` the `load()` call will be omitted.
* `ajsPath`: override the default analytics.min.js location


### snippet.min(options)

Returns the minified version of the snippet.


## Development

### Installation + QA
```
nvm use
yarn install
make lint
make test
```

### Running tests in Saucelabs
```
SAUCE=true make test
```

## Releasing
1. Publish to `npm`
```sh
git checkout master && git pull --ff-only
npm version <patch|minor|major>
git push --follow-tags
make build
npm publish
```
2. Create a [new github release](https://github.com/segmentio/snippet/releases).

3. Bump package version on [segmentio/app](https://github.com/segmentio/app/blob/main/packages/app/package.json).

4. Update _all_ example snippets on [public docs repo](https://github.com/segmentio/segment-docs) via search + replace 
- Get example snippet by runnings `yarn fixture` and observing generated `tmp.fixture.*.js` files. 
- Tip: double-check that the fixture's `SNIPPET_VERSION` refers to the new npm version.
npm package: @segment/tracktor
Description: <img src="logo.jpg" width="30%" height="30%" />
Latest version: 0.12.1

## Tracktor

<img src="logo.jpg" width="30%" height="30%" />

Tracktor is a standalone script that pairs with the [Segment Visual Tracker](https://github.com/segmentio/vistag) to instrument tracking into websites.

It takes the tagger's tracking instrumentation specs and binds to a subset of dom element events. When the event is fired, the tracking event is sent to the website's instrumented AJS tracker.

## Trying it out

You can develop on Tracktor easily by using the sample application.

```
yarn start
```

## Building the script

```
yarn build:tracktor
```

## Running integration tests
To run integration tests (that run in a headless chrome environment for blackbox testing) run

```
yarn test
```
## Release
To release a new version of Tracktor follow these steps

1. Run `npx release-it` and follow the prompts to release the tracktor module to npm

2. Publish `analytics.js-integrations` visual tagger integration by updating the tracktor version of the visual tagger integration hosted in the [analytics.js-integrations repo](https://github.com/segmentio/analytics.js-integrations/blob/master/integrations/visual-tagger/package.json#L13) to reflect
  the version published in step 1 and running `npm publish`

3. PR `analytics.js-private` to [update the version of the visual tagger integration](https://github.com/segmentio/analytics.js-private/blob/master/package.json#L168) published in step 2 and [follow the release train process laid out in "Releasing analytics.js"](https://paper.dropbox.com/doc/Releasing-Analytics.js--Apzb30eYwpnpNg5_pzahG4~eAg-QYiKKIDvhsZk2c0bOTEhp)

4. Actively monitor the [integration dashboard](https://segment.datadoghq.com/dashboard/ub6-dvn-xst/vt-integration-dashboard?from_ts=1575271168995&live=true&tile_size=m&to_ts=1575357568995) across release tiers until the integration is fully rolled out