open-index/open-npm huggingface dataset:
npm package: @khulnasoft/schemaify
Description: Browserify transform for compiling JSON schemas at build time using AJV
Author: Md Sulaiman
Latest version: 0.1.0

# schemaify

Browserify transform for compiling JSON schemas at build time using AJV and `ajv-pack`

## Installation

The package is released to npm as `@khulnasoft/schemaify`:

```
npm install @khulnasoft/schemaify -D
```

## Usage

In the default configuration, the transform is applied to all files with a `.schema` extension. The transformed module will export the packed AJV `validate` function.

In your application:

```js
var validateFoo = require('./foo.schema')

var ok = validateFoo({ foo: true })
if (!ok) {
  console.log(validateFoo.errors)
  throw new Error('Foo did not validate')
}
```

When bundling:

```js
var browserify = require('browserify')

var b = browserify()
b.add('app.js')
b.transform('@khulnasoft/schemaify')
b.bundle(function (err, src) {
  // consume bundle
})
```

### Defining schemas

Schemas are expected to be defined in JSON format and saved as `.schema` files:

```json
{
  "type": "string",
  "maxLength": 128
}
```

## Options

The transform accepts the following options as its 2nd arguments:

### `secure`

By default, `schemaify` only compiles ["secure" schemas][secure]. This can be disabled by passing `secure: false` to the transform.

[secure]: https://github.com/ajv-validator/ajv/tree/521c3a53f15f5502fb4a734194932535d311267c#security-considerations

### `matcher`

By default, `schemaify` only compiles files with a `.schema` extension. If you have different requirements you can pass a Regexp string to `matcher` for the transform to use.

**Important caveat**: Due to the way that Browserify handles JSON files, you currently __cannot use `.json` files__ for storing your schemas, as this would make these files subject to another set of rules that would conflict with.

## Releasing a new version

New versions can be released using `npm version <patch|minor|major>`. Make sure you are authenticated against the `@khulnasoft` scope with npm.

## License

Copyright 2020 Md Sulaiman - Available under the MIT License
npm package: @khulnasoft/sdk
Description: SDK for generating and embedding KhulnaSoft projects.
Author: KhulnaSoft Ltd.
Latest version: 1.0.0

# KhulnaSoft SDK

The KhulnaSoft JavaScript SDK lets you programmatically create KhulnaSoft projects to be opened in a new window or embedded in your docs, example pages, or blog posts.

## Documentation

Check out our SDK documentation on developer.khulnasoft.com:

- [SDK overview](https://developer.khulnasoft.com/platform/api/javascript-sdk)
- [Options reference](https://developer.khulnasoft.com/platform/api/javascript-sdk-options)
- [Controlling embeds](https://developer.khulnasoft.com/platform/api/javascript-sdk-vm)

## Reporting issues

- Issues with the SDK can be filed at https://github.com/khulnasoft/pkg.khulnasoft.com/issues

## Development

We use `npm` and Node 16+.

```sh
# Install dependencies
npm install

# Start a development server to explore examples
npm start

# Run unit tests
npm test

# Run end-to-end tests with mock server
npm run test:e2e

# Run end-to-end tests against khulnasoft.com
KHULNASOFT_SERVER_ORIGIN=https://khulnasoft.com npm run test:e2e

# Generate the 'bundles' and 'types' folders
npm run build
```
npm package: @khulnasoft/stylelint-config
Description: KhulnaSoft Stylelint base configuration
Author: KhulnaSoft
Latest version: 1.0.1

# @khulnasoft/stylelint-config

This is the base Stylelint configuration used to enforce coding standards for styles in [KhulnaSoft](https://about.gitlab.com/)'s projects.

# Usage

1. Add the configuration to your dev dependencies:

```sh
yarn add --dev @khulnasoft/stylelint-config stylelint postcss
```

2. Extend the config in your `.stylelintrc`:

```
{
   "extends": "@khulnasoft/stylelint-config"
}
```

## Release management

This project automatically publishes the `main` branch using [semantic-release](https://github.com/semantic-release/semantic-release).
If a new commit/merge request is merged into `main` and it's commit(s) follows the [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines),
a release will be automatically generated and published. Commits that do not follow the convention will be ignored and a release will not be made for them.
npm package: @khulnasoft/tsconfig
Description: Base tsconfig.json for KhulnaSoft TypeScript projects
Author: Md Sulaiman
Latest version: 4.0.1


# KhulnaSoft tsconfig

[![npm](https://img.shields.io/npm/v/@khulnasoft/tsconfig.svg)](https://www.npmjs.com/package/@khulnasoft/tsconfig)
[![downloads](https://img.shields.io/npm/dt/@khulnasoft/tsconfig.svg)](https://www.npmjs.com/package/@khulnasoft/tsconfig)
[![build](https://travis-ci.org/khulnasoft-lab/tsconfig.svg?branch=master)](https://travis-ci.org/khulnasoft-lab/tsconfig)
[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)](https://github.com/prettier/prettier)

Base tsconfig.json for TypeScript projects at KhulnaSoft.
It only includes compiler options that make TypeScript more strict.
It does not set any project-specific or environmental settings.

## Usage

```
npm install --save-dev @khulnasoft/tsconfig
```

Then add this tsconfig.json:

```json
{
  "extends": "./node_modules/@khulnasoft/tsconfig/tsconfig.json"
}
```

## Making changes

```
npm link
cd <project>
npm link @khulnasoft/tsconfig
npm run lint
```

## Publish a new version

Follow [semver](http://semver.org/).

```
npm version major|minor|patch
git push
git push --tags
npm publish
```