open-index/open-npm huggingface dataset:
npm package: @progress/jsdo-angular
Description: The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular. This will provide a seamless integration between OpenEdge (Progress Data Object) with Angular.
Author: Progress Software
Latest version: 6.0.0

# Progress Data Source for Angular
The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular. This will provide a seamless integration between OpenEdge (Progress Data Object) with NativeScript and Angular". 

### Documentation
Progress® Data Objects, which include the JSDO on the client, represent the Progress-released implementation of Cloud Data Objects. For more information on the latest release, see the <a href="https://documentation.progress.com/output/pdo">Progress Data Objects Guide and Reference.</a>

The Data Source can be used by apps built using NativeScript, Angular and Node.

### License
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
npm package: @progress/jsdo-nativescript
Description: The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular. This will provide a seamless integration between OpenEdge (Progress Data Object) with NativeScript
Author: Progress Software
Latest version: 5.0.0

# Progress Data Source for NativeScript
The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular. This will provide a seamless integration between OpenEdge (Progress Data Object) with NativeScript"  

### Documentation
Progress® Data Objects, which include the JSDO on the client, represent the Progress-released implementation of Cloud Data Objects. For more information on the latest release, see the <a href="https://documentation.progress.com/output/pdo">Progress Data Objects Guide and Reference.</a>

The Data Source can be used by mobile apps built using NativeScript.

### License
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
npm package: @progress/jsdo-node
Description: The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular and Node.js. This will provide a seamless integration between OpenEdge (Progress Data Object) with Node.js.
Author: Progress Software
Latest version: 5.0.0-2018-05-11-00002

# Progress Data Source for Node
The Progress Data Source is a TypeScript implementation - Progress Data Source class for NativeScript, Angular. This will provide a seamless integration between OpenEdge (Progress Data Object) with NativeScript and Angular". 

### Documentation
Progress® Data Objects, which include the JSDO on the client, represent the Progress-released implementation of Cloud Data Objects. For more information on the latest release, see the <a href="https://documentation.progress.com/output/pdo">Progress Data Objects Guide and Reference.</a>

The Data Source can be used by apps built using NativeScript, Angular and Node.

### License
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
npm package: @progress/kendo-theme-tasks
Description: Build utility for @progress/kendo-themes
Author: Progress
Latest version: 1.17.6
Deprecated: This package is deprecated and will no longer receive updates.

# Kendo UI Theme Tasks

The Kendo UI `theme-tasks` package is a utility library for developing and building `@progress/kendo-theme-*` packages.

## Installation

1. Install the package as a dev dependency:

```sh
    npm install @progress/kendo-theme-tasks --save-dev
```

2. Install the preferred sass compiler(`node-sass` or `sass`):

```sh
    npm install sass
    npm install node-sass
```

3. If using npm version < 7 make sure that peer dependencies are installed:

```sh
    npm install postcss postcss-calc autoprefixer
```

## Usage

The package allows you to compile Kendo themes from SCSS or JSON through the `kendoSassBuild` and `kendoJsonBuild` functions.

### Building from SCSS

A Kendo theme can be compiled to CSS from SCSS source with predefined configuration options (package importer, postcss, postcss-calc and autoprefixer) through the `kendoSassBuild()` method:

1. Import the theme:

```scss
    @import "~@progress/kendo-theme-default/dist/all.scss";
```

2. Compile to CSS:

```js
    const { kendoSassBuild } = require('@progress/kendo-theme-tasks/src/build/kendo-build');

    function buildStyles(cb) {
        kendoSassBuild({
            file: './sass/styles.scss',
            output: {
                path: './wwwroot/css'
            },
            sassOptions: {
                compiler: 'node-sass',
                minify: true
            }
        });

        cb();
    }

    exports.buildStyles = buildStyles;
```

### Building from JSON

A Kendo theme or a custom theme swatch can be compiled to CSS from JSON schema with predefined configuration options (package importer, postcss, postcss-calc and autoprefixer) through the `kendoJsonBuild()` method:

1. Utilize [one of the existing theme swatches](https://github.com/telerik/kendo-themes/blob/develop/packages/default/lib/swatches/default-main.json) or create a new one by following [the schema](https://github.com/telerik/kendo-theme-tasks/blob/develop/lib/schemas/kendo-swatch.json).

2. Compile the JSON schema to CSS:

```js
    const { kendoJsonBuild } = require('@progress/kendo-theme-tasks/src/build/kendo-build');

    function buildStyles(cb) {
        kendoJsonBuild({
            file: 'scss/theme.json',
            output: {
                path: 'dist/'
            },
            sassOptions: {
                compiler: 'node-sass',
                minify: true
            }
        });

        cb();
    }

    exports.build = buildStyles;
```
npm package: @progress/semantic-prerelease
Description: A set of plug-ins for semantic-release that provide a workflow for prerelease versions.
Author: Telerik
Latest version: 3.0.2
Deprecated: Discontinued package. Please use semantic-release.

# semantic-prerelease

A set of scripts for [semantic-release](https://github.com/semantic-release/semantic-release) that allow publishing of prerelease versions from branches.

This projects allows you to push prerelease package versions to NPM, hidden behind a dist-tag, and trigger deployments by fast-forwarding a release branch.

## Prerequisites

- semantic-release **6.x+**
- git **2.13+** (used for tag parsing)

This project has been tested in Travis-CI and Jenkins builds.

## Usage

1. Install the node module through the following command:

       npm install --save-dev @progress/semantic-prerelease

2. Describe the branches that will publish prerelease versions.
     In this example, commits in the `develop` branch pushes prerelease versions to the `dev` dist-tag. Use `fallbackTags` to bootstrap the versions.

        // package.json
        "release": {
          "branchTags": {
            "develop": "dev"
          },
          "fallbackTags": {
            "dev": "latest"
          }
        }

3. Configure semantic-release to use the included plug-ins:

        // package.json
        "release": {
          "analyzeCommits": "@progress/semantic-prerelease/analyzeCommits",
          "generateNotes": "@progress/semantic-prerelease/generateNotes",
          "getLastRelease": "@progress/semantic-prerelease/getLastRelease",
          "verifyConditions": "@progress/semantic-prerelease/verifyConditions",
          "verifyRelease": "@progress/semantic-prerelease/verifyRelease"
        }

4. Use `semantic-prerelease publish` instead of `npm publish` in the end of your build. This publishes the prerelease versions behind dist-tags.

5. (Optionally) Publish scoped packages as public by using `semantic-prerelease publish --public`

With the above setup, new official releases (bearing the `latest` dist-tag) can be published from `master` by fast-forwarding it to `develop`:

    git checkout master && git merge --ff-only develop && git push

> Your first official release will be published with version 0.1.0 to enable automatic releases during initial development. You must mark a commit as a [major release](https://github.com/semantic-release/semantic-release#major-breaking-release) to bump the major version to 1. This is different than vanilla semantic-release where your first release is 1.0.0