open-index/open-npm huggingface dataset:
npm package: @orientais/vscode
Description: TypeScript definitions for the Orientais Code extension API (based on the VS Code extension API, MIT)
Author: Orientais Software / Orientais Code
Latest version: 1.115.0

# @orientais/vscode

TypeScript definitions for the **Orientais Code** extension API, intended for extension development and CI type checking.

## License and Notice

- This npm package is built and published by **Orientais Software / Orientais Code**.
- The type information is derived from the open-source Visual Studio Code extension API definitions (following the `vscode.d.ts` source). Copyright for the upstream API definitions belongs to **Microsoft Corporation** and is released under the **MIT** license.
- This package is provided for type information only and does not guarantee runtime behavior or API stability.

## Usage

```bash
npm install --save-dev @orientais/vscode
```

In your `tsconfig.json`:
```json
{
  "compilerOptions": {
    "types": ["orientais__vscode"]
  }
}
```

Then in your extension:
```ts
import type { Disposable, ExtensionContext } from 'vscode';
```
npm package: @oriented/cli
Description: A command line interface for Oriented.
Author: Sean Donnelly
Latest version: 0.1.1

# @oriented/cli
A command line interface for building Oriented apps.

## Installation 
```sh
$ npm install -g @oriented/cli
```
## Usage
```sh
$ oriented-cli --help
```
### Getting Started
```sh
$ oriented-cli new APPNAME
$ cd APPNAME
$ npm start
```
npm package: @orientesh/dispack
Description: the client for Oriente FE distribution pack.
Author: mathewwang
Latest version: 1.0.3

# egg-dispack-client

[![NPM version][npm-image]][npm-url]
[![build status][travis-image]][travis-url]
[![Test coverage][codecov-image]][codecov-url]
[![David deps][david-image]][david-url]
[![Known Vulnerabilities][snyk-image]][snyk-url]
[![npm download][download-image]][download-url]

[npm-image]: https://img.shields.io/npm/v/egg-dispack-client.svg?style=flat-square
[npm-url]: https://npmjs.org/package/egg-dispack-client
[travis-image]: https://img.shields.io/travis/eggjs/egg-dispack-client.svg?style=flat-square
[travis-url]: https://travis-ci.org/eggjs/egg-dispack-client
[codecov-image]: https://img.shields.io/codecov/c/github/eggjs/egg-dispack-client.svg?style=flat-square
[codecov-url]: https://codecov.io/github/eggjs/egg-dispack-client?branch=master
[david-image]: https://img.shields.io/david/eggjs/egg-dispack-client.svg?style=flat-square
[david-url]: https://david-dm.org/eggjs/egg-dispack-client
[snyk-image]: https://snyk.io/test/npm/egg-dispack-client/badge.svg?style=flat-square
[snyk-url]: https://snyk.io/test/npm/egg-dispack-client
[download-image]: https://img.shields.io/npm/dm/egg-dispack-client.svg?style=flat-square
[download-url]: https://npmjs.org/package/egg-dispack-client

<!--
Description here.
-->

## Install

```bash
$ npm i egg-dispack-client --save
```

## Usage

```js
// {app_root}/config/plugin.js
exports.dispackClient = {
  enable: true,
  package: 'egg-dispack-client',
};
```

## Configuration

```js
// {app_root}/config/config.default.js
exports.dispackClient = {
};
```

see [config/config.default.js](config/config.default.js) for more detail.

## Example

<!-- example here -->

## Questions & Suggestions

Please open an issue [here](https://github.com/eggjs/egg/issues).

## License

[MIT](LICENSE)
npm package: @orientesh/frontend
Description: A eggjs frontend for bulb project
Author: Oriente FE team
Latest version: 1.0.25

# @orientesh/frontend

A frontend framework for bulb-project**[WIP]**.

## Table of Contents

* [Motivation](#motivation)
* [Design Goals](#design\ goals)
* [Implementation](#implementation)
* [Webpack](#webpack)
* [Seaweedfs](#seaweedfs)
* [CDN](#cdn)(TODO)

## Motivation

To get our hands dirty in server-side rendering, it's quite obvious we'd need a Node.js layer. Alas, adding an extra layer for server-side rendering simply brings more complexity to the whole system and more chores for deployment.

## Design Goals

* **Bulb is uniform**. By "uniform", we mean we'd want to free application developers from managing fragmented chores.

* **Bulb is extensible**. Bulb is bult on top of Egg.js, which is plugable. In fact, any existing plugins work directly in Bulb.

* **Bulb is distributed**. Any serious softwares are distributed. This is the only way to robustness.

* **Bulb is fast**.

## Implementation

Hence, we've built a frontend on top of eggjs to take care of some fragile tasks:

* Transpilation & bundling.

* Preserve transpiled assets:
    * Store server-side assets to remote distributed file system(in our case, seaweedfs)
    * Push static client-side assets to CDN(TODO)

These tasks are handled by bulb online and yes, the build step is performed online.

Nonetheless, duplications of above tasks occur when deploying more than a single bulb application. In order to resolve this problem, we've chosen Zookeeper for distributed synchronization:

* Take the above tasks as a whole single mono task, let's say, `pack`, which succeeds when all sub tasks succeed. It doesn't matter if it's halfway done, since those emitted/synced files will either be obsoleted or overwritten.

* Each bulb server will be likely to execute `pack`. But before it does, it first proposes pack to a Zookeeper server, if it is the chosen leader, then it starts packing; otherwise it becomes a follower and waits.

* Emitted server-side assets are fetched on demand, by other followers.

When `pack` is done, every server is ready.

## Webpack

TODO

## SeaweedFS

TODO

## CDN

TODO
npm package: @oriflame/babel-preset
Description: Babel preset for oriflame projects.
Author: Jan Silhan
Latest version: 5.15.15

# `@oriflame/babel-preset`

## Installation

```sh
npm install --save-dev @oriflame/babel-preset @babel/core
yarn add --dev @oriflame/babel-preset @babel/core
```

## Usage

### babelrc

```json
{
  "presets": [
    [
      "@oriflame/babel-preset",
      {
        "react": true
      }
    ]
  ]
}
```

### Options

- react `boolean`
  - Enable react preset
- modules `boolean`
  - Enables modules transpilation
- library `boolean`
  - Enables optimizations for library
- graphql `boolean`
  - Add support for graphql
- removePropTypes `boolean`
  - Removes prop types from source code
- targets `Record<string, string> | string[] | string`
  - env targets (see:
    [@babel/preset-env#targets](https://babeljs.io/docs/en/babel-preset-env#targets))
- srcFolder `string`
  - Change default source folder
  - default: `src`
- env `object`
  - Change env setting
  - see: [@babel/preset-evn](https://babeljs.io/docs/en/babel-preset-env)

### Using core-js

We support core-js polyfills.

See: [babel documentation](https://babeljs.io/docs/en/babel-preset-env#usebuiltins-entry).
npm package: @oriflame/config-danger
Description: Reusable Danger.js scripts.
Author: Silhan Jan
Latest version: 5.15.15

# @oriflame/config-danger]

## Usage

dangerfile.js

```javascript
import {
  checkForInvalidLocks,
  checkForConventionalPrefix,
  checkForConventionalSquashCommit,
} from '@oriflame/config-danger';

checkForInvalidLocks();
checkForConventionalPrefix();
checkForConventionalSquashCommit();
```
npm package: @oriflame/constant-moduleids-webpack-plugin
Description: Webpack plugin for generating constant hashed moduleIds for use with DLL plugin.
Author: Jan Novotny @ecl1ps
Latest version: 1.1.0

﻿In its basic form [HashedModuleIdsPlugin](https://webpack.js.org/plugins/hashed-module-ids-plugin/) and [DeterministicModuleIdsPlugin](https://webpack.js.org/configuration/optimization/#optimizationmoduleids) both use `Module.identifier()` as a source for final moduleId. It is true that generated ids by these plugins are based on module name/path but it is not always only the module name. In some cases webpack internally creates a `ConcatenatedModule` for multiple internal modules for one main module and then `identifier` contains something like `<module name>|<hash of all internal modules>`.

This id can change between multiple builds even when the version of some dependency (main module) doesn't change. It is probably caused by using different number of internal modules. And this volatility is a problem when the result bundle is used as a DLL with `DLLReferencePlugin`. Every consumer would have to rebuild its bundle every time the dll bundle would change (every change, even patch, would have to be treated as a breaking).

This plugin replaces the use of `Module.identifier()` with `Module.libIdent()` (resp. `getFullModuleName` with `getShortModuleName`) which results in **only the name of module being used**. That way **moduleIds never change and can be relied on**.
npm package: @oriflame/conventional-changelog
Description: Conventional changelog preset for oriflame and associated projects.
Author: Jan Silhan
Latest version: 1.2.58

# @oriflame/conventional-changelog

Oriflame's commit message guidelines and changelog structure. _Now with more emojis!_

## Azure devops prefix

This changelog accounts with azure devops PR message format. And will release accordingly to the following documentation.

## Commit Message Format

The commit message format consists of a **type**, optional **scope** in parenthesis, and a required
**message**:

```
<type>: <message>
<type>(<scope>): <message>
Merged PR 1: <type>(<scope>): <message>
Merged PR 1: <type>: <message>
```

> ⚠️
> Azure devops message format is allowed but not required.

### Type

The type is a way to group commits and flag semver changes. The following types must be used when
prefixing your commit message.

#### Major

- `break`, `breaking` - A _major_ breaking change.
- `release` - Not a breaking change but bumps the _major_ version.

#### Minor

- `new` - Introduces a new feature.
- `update` - Updates an existing feature.
- `feature` - Both a new and update.

#### Patch

- `fix` - Fixes existing functionality.
- `deps` - Bumps dependencies.
- `docs` - Updates documentation.
- `revert` - Reverts previous or broken code.
- `style` - Updates visual styles, like CSS.
- `security` - Improves security.
- `type`, `types` - Updates type system related syntax (TS/Flow).
- `misc` - Catch all for commits that don't align with other types.

#### Skip

- `ci` - Changes to the CI pipeline.
- `build` - Changes to the build system.
- `test`, `tests` - Changes to tests or the testing framework.
- `internal` - Internal changes not critical for the consumer.

### Scope

The scope is optional but useful in defining granularity in a commit message. Scope is ideally used
to target a specific feature or module within the project, for example:
`new(Button): Add a new Button component`.

Scopes will appear in the changelog before each line item and accept the following characters:
`A-Z`, `a-z`, `0-9`, `-`, `.`, `,`, and spaces.

### Message

The message contains a succinct description of the change:

- Use the imperative, present tense: "change" not "changed" nor "changes".
- Capitalize first letter of message.
- Trailing punctuation (period) is not required, but preferred.

## Example

Given the following commit messages:

```
new(Button): Add new Button component
update(Modal,Tooltip): Refactor accessibility support
ci: Add DangerJS to pipeline
test: Add missing tests for a handful of files
fix(auth): Fixed a bug with the authentication flow
```

Would generate the following changelog:

---

## 1.2.3 - 2019-01-01

#### 🚀 Updates

- **[Button]** Add new Button component ([a1b2c3d][fake-commit])
- **[Modal,Tooltip]** Refactor accessibility support ([a1b2c3d][fake-commit])

#### 🐞 Fixes

- **[auth]** Fixed a bug with the authentication flow ([a1b2c3d][fake-commit])

#### 🛠 Internals

- Add DangerJS to pipeline ([a1b2c3d][fake-commit])
- Add missing tests for a handful of files ([a1b2c3d][fake-commit])

[fake-commit]: #example
npm package: @oriflame/conventional-changelog-lint-config
Description: Conventional changelog lint config oriflame
Author: Jan Šilhan
Latest version: 1.1.60

# @oriflame/conventional-changelog-lint-config

Config for [oriflame preset](../conventional-changelog).

## Getting started

```sh
# Install commitlint cli and conventional config
npm install --save-dev @commitlint/cli @oriflame/conventional-changelog-lint-config
# Or use yarn
yarn add --dev @commitlint/cli @oriflame/conventional-changelog-lint-config

# Configure commitlint to use conventional config
echo "module.exports = {extends: ['@oriflame/conventional-changelog-lint-config']}" > commitlint.config.js
```

To lint commits before they are created you can use Husky's 'commit-msg' hook:

```json
{
  "husky": {
    "hooks": {
      "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
    }
  }
}
```

## Further instructions

[commitlint](https://github.com/conventional-changelog/commitlint)
npm package: @oriflame/eslint-config
Description: Reusable ESLint config for oriflame project
Author: Silhan Jan
Latest version: 5.15.15

# `@oriflame/eslint-config`

Sharable configuration for eslint.

## Installation

```sh
npm install --save-dev @oriflame/eslint-config eslint
yarn add --dev @oriflame/eslint-config eslint
```

## Usage

`.eslintrc.js`:

```javascript
module.exports = {
  root: true,
  extends: [
    'oriflame',
    'oriflame/node',
    'oriflame/typescript',
    'oriflame/future',
    'oriflame/prettier',
  ],
};
```

## Presets

- oriflame
  - Base preset containing bare configuration
- node
  - Enable rules for node
- typescript
  - Enable support for typescript
- nextjs
  - Enable support for next
- future
  - Enable esnext support
- prettier
  - Enable integration with prettier
  - This must be last
npm package: @oriflame/jest-preset
Description: Jest preset for lumos configured projects.
Author: Jan Silhan
Latest version: 5.15.15

# @oriflame/jest-preset

Sharable jest preset.

## Installation

```sh
npm install --save-dev @oriflame/jest-preset jest
yarn add --dev @oriflame/jest-preset jest
```

## Usage

`jest.config.js`:

```javascript
module.exports = {
  preset: '@oriflame/jest-preset',
};
```
npm package: @oriflame/prettier-config
Description: Reusable Prettier config for lumos configured projects.
Author: Jan Silhan
Latest version: 5.15.15

# @oriflame/prettier-config

## Installation

```sh
npm install --save-dev @oriflame/prettier-config prettier
yarn add --dev @oriflame/prettier-config prettier
```

## Usage

`package.json`:

```json
{
  "prettier": "@oriflame/prettier-config"
}
```

`.prettierrc`:

```javascript
module.exports = '@oriflame/prettier-config';
```

or you can override part of the config

```javascript
module.exports = {
  ...require('@oriflame/prettier-config'),
  semi: false,
};
```
npm package: @oriflame/semantic-release-config
Description: Semantic release config used inside Oriflame and mainly focused on azure DevOps. With conventional [**Oriflame changelog**](../conventional-changelog).
Latest version: 2.1.77

# @oriflame/semantic-release-config

Semantic release config used inside Oriflame and mainly focused on azure DevOps.
With conventional [**Oriflame changelog**](../conventional-changelog).

[**semantic-release**](https://github.com/semantic-release/semantic-release) shareable config to publish npm packages with [GitHub](https://github.com).

## Plugins used

This [shareable configuration](https://github.com/jedmao/semantic-release-npm-github-config/blob/master/.releaserc.json) uses the following plugins:

- [`@semantic-release/commit-analyzer`](https://github.com/semantic-release/commit-analyzer)
- [`@semantic-release/release-notes-generator`](https://github.com/semantic-release/release-notes-generator)
- [`@semantic-release/changelog`](https://github.com/semantic-release/changelog)
- [`@semantic-release/npm`](https://github.com/semantic-release/npm)
- [`@semantic-release/git`](https://github.com/semantic-release/git)

## Install

```bash
npm install --save-dev semantic-release @oriflame/semantic-release-config
```

## Usage

The shareable config can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):

```json
{
  "extends": "@oriflame/semantic-release-config",
  "branch": "master"
}
```

## Generating changelog

To enable changelog generation set env variable `GENERATE_CHANGELOG` to true;
npm package: @oriflame/tsconfig
Description: Pre-packaged tsconfig.json's for oriflame configured projects.
Author: Jan Silhan
Latest version: 5.15.15

# @oriflame/tsconfig

Sharable typescript configuration.

## Installation

```sh
npm install --save-dev @oriflame/tsconfig typescript
yarn add --dev @oriflame/tsconfig typescript
```

## Usage

`tsconfig.json`:

```json
{
  "extends": "@oriflame/tsconfig"
}
```

Or

```json
{
  "extends": "@oriflame/tsconfig/tsconfig.workspace.json"
}
```
npm package: @origami-network/cli-step-version
Description: Module that helps generate build and publish version.
Author: Bartlomiej Dubas
Latest version: 0.0.0

[![Build Status](https://travis-ci.org/origami-network/node-cli-step-version.svg?branch=master)](https://travis-ci.org/origami-network/node-cli-step-version)
[![Coverage Status](https://coveralls.io/repos/github/origami-network/node-cli-step-version/badge.svg?branch=master)](https://coveralls.io/github/origami-network/node-cli-step-version?branch=master)

Get Version
==

Helper command line tool to get version from the `package.json` file in the current working directory.

It can be used as continuous integration/delivery step to return versions to the pipeline.


## Usage

The simple usage is to define custom script that will install and run the command at once.

In the `package.json` add new script:

```json
{
    ...
    "scripts": {
        "cli-step-version": "npm install --no-save --silent @origami-network/cli-step-version && cli-step-version"
        ...
    }
    ...
}
```

Now it is possible to get version from command line.

```shell
> npm run cli-step-version
```

As the result the last two lines on the console will display version for:

 * **build** - including build number and branch that can be used to uniquely associate output with the build process. 
 * **publish** - the version that should be used to publish artifacts in registries. Like node package to NPM registry. 

This will allow to run the script without calling `npm install` before.


### Parameters

It is possible to pass additional parameters to the script when calling `npm run`, by adding `--` and the arguments of the script:

 * `-n`, `--build-number <value>` - sequential number, added as the last digit in the version number,
 * `-b`, `--build-branch <name>` - additional value indicating the branch or label for the version, added after eventual build number separated by "`-`" character.

In addition, fallowing informational parameters can be used:

 * `-h`, `--help` - output usage information,
 * `-V`, `--version` - output version of the script.


## Examples

### Command line

if the `package.json` has defined version `1.2.3`, then calling fallowing command:

```shell
> npm run cli-step-version -- -build-number 10 -build-branch feature/new-function
```

Will provide two last line of the output:

```

1.2.3.10-feature-new-function
1.2.3
```


### Jenkinsfile

For Windows slave node add fallowing code to `Jenkinsfile`.

```groovy
def output = bat (
    script: "npm run cli-step-version -- --build-number ${env.BUILD_NUMBER} --build-branch ${env.BRANCH_NAME}",
    returnStdout: true
).tokenize().takeRight(2)
def version = [
    build: output.first(),
    publish: output.last()
]
```

On Un*x slave nodes `bat` step should be replaced with `sh` step.

> By default Jenkins script policy do not allow methods `takeRight` and `first`. After first run they need to be accepted.
npm package: @origami/deploy-heroku
Description: Small CLI utility for deploying Origami apps to Heroku
Author: Tristan Matthias
Latest version: 0.0.2

# Origami - Deploy Heroku

A small CLI utility that deploys a Origami app to Heroku


## Usage
```
deploy-heroku <app>

Deploy an Origami app on Heroku

Options:
  --help           Show help                    [boolean]
  --version        Show version number          [boolean]
  --skipSetup, -s  Skip creation of the app     [boolean] [default: false]
  --mongo          Attach a mLab Mongo database [boolean]
```
npm package: @origamicore/cli
Description: OrigamiCore CLI
Author: origamicore.com@gmail.com
Latest version: 3.1.11

# Typescript OrigamiCore CLI (OCCLI)

[OrigamiCore](https://www.npmjs.com/package/@origamicore/core)

[Old OrigamiCore](https://www.npmjs.com/package/origamicore)

## Installation

OriCli requires [Node.js](https://nodejs.org/) v16+ to run.

```sh
npm install @origamicore/cli -g
```

### Mongo Database Managment
```sh
occli mongo
```

### Create Projects

```sh
occli --new projectName

occli -n projectName
```

### Create Service

```sh
occli --addmodule moduleName
occli --a moduleName
```

### Start Project

```sh
occli dev
```

### Start Project as Bunjs

```sh
occli bun
```

### UI Editor

```sh
occli --ui {{port:default 4000}}
```
npm package: @origamicore/core
Description: OrigamiCore is a powerful Node.js framework that allows you to develop your project maintainable, fast and easily
Author: OrigamiCore
Latest version: 4.2.3

# TypeScript OrigamiCore
OrigamiCore is a powerful Node.js framework that allows you to develop your project maintainable, fast and easily

[Old Repository](https://www.npmjs.com/package/origamicore)
## Installation

OrigamiCore requires [Node.js](https://nodejs.org/) v14+ to run.
 
install CLI
```sh
npm install @origamicore/cli@latest -g
```

### Create Projects

```sh
occli --new projectName
occli -n projectName
```

### Add Module

```sh
occli --addservice moduleName
occli -a moduleName
```

### Start Project

```sh
occli dev
```

### Start Project as Bunjs

```sh
occli bun
```

### UI Editor

```sh
occli --ui {{port:default 4000}}
```

## Plugins
OrigamiCore is currently extended with the following plugins.
Instructions on how to use them in your own application are linked below.

| Plugin | README |
| ------ | ------ |
| Endpoint(express,socket) | [https://www.npmjs.com/package/@origamicore/endpoint] | 
| MongoDb | [https://www.npmjs.com/package/@origamicore/mongo] | 
| Redis | [https://www.npmjs.com/package/@origamicore/redis] |  
| EOSIO Hyperion | [https://www.npmjs.com/package/@origamicore/hyperion] | 
| Semaphore  | [https://github.com/origamicore/semaphore] | 
| Google OAuth  | [https://github.com/origamicore/google-oauth] | 

## Projects

<img src="https://www.xpell.io/icons/logo.ico" width="20"/>[Xpell Game](https://www.xpell.io/)

<img src="https://ajor.io/favicon.ico" width="20"/>[Ajor Block Explorer](https://ajor.io/)

<img src="https://areaxnft.com/icons/areax-logo.png" width="20"/>[Telos NFT Market](https://areaxnft.com/)


## Opensource Project

<img src="https://origamicore.com/assets/yahtzee.96a4278a.png" width="15"/> [Yahtzee](https://yahtzeefront.origamicore.com/join-game)

<img src="https://origamicore.com/assets/evac.d905c30d.svg" width="15"/>[Evak](https://evacfront.origamicore.com/)
npm package: @origamicore/endpoint
Description: OrigamiCore Endpoint
Author: vahid.hossaini@gmail.com
Latest version: 1.1.9

# TypeScript TsOriEndpoint

## Installation
OrigamiEndpoint requires [OrigamiCore](https://www.npmjs.com/package/@origamicore/core)  to run.
```sh
npm install @origamicore/core
npm install @origamicore/endpoint
```
## BunJS Sample 
[Run BunJS](https://github.com/origamicore/endpoint/blob/main/sample/bunSample.ts)

## Samples
[Run Express And Socket](https://github.com/origamicore/endpoint/tree/main/sample)

## Create New Project
[The Article](https://medium.com/@origamicore.com/origami-endpoint-f82692b7e6c9)
npm package: @origamicore/hyperion
Description: Blockchain Hyperion
Latest version: 1.0.4

# TypeScript Origami Hyperion


## Installation
OrigamiHyperion requires [OrigamiCore](https://www.npmjs.com/package/@origamicore/core)  to run.
```sh
npm install @origamicore/core
npm install @origamicore/hyperion
```
## Samples
[Hyperion Sample](https://github.com/origamicore/hyperion/tree/main/sample)

## Create New Project
[The Article](https://medium.com/@origamicore.com/origami-hyperion-952aba9fd751)
npm package: @origamicore/orm
Description: OrigamiCore ORM
Author: vahid.hossaini@gmail.com
Latest version: 1.0.27

# TypeScript TsOriORM

## Installation
OrigamiORM requires [OrigamiCore](https://www.npmjs.com/package/@origamicore/core)  to run.
```sh
npm install @origamicore/core
npm install @origamicore/orm
```