open-index/open-npm huggingface dataset:
npm package: @opsystech/lidar-template
Description: A blank schematics
Latest version: 0.0.8

# Lidar basic schematic

With this repository you can create your lidar project reference easily.
the template is based on lidar-client package. 
(to be used with lidar-server package)

### Testing

fist create a fresh new angular project:

```bash
ng new  empty-angular --style=scss --routing=true
```

then add the lidar template

```bash
cd empty-angular
ng add lidar-template
```

and try it!:

```bash
ng serve
```
you should see a basic UI for later use.
npm package: @opt-tech/gtm-json-converter
Description: Google Tag Manager がエクスポートした JSON をエクセルで開ける CSV に変換します
Latest version: 1.0.7

# GTM JSON Converter

[![CircleCI](https://circleci.com/gh/opt-tech/gtm-json-converter.svg?style=shield)](https://circleci.com/gh/opt-tech/gtm-json-converter)
[![npm](https://img.shields.io/npm/v/@opt-tech/gtm-json-converter.svg)](https://www.npmjs.com/package/@opt-tech/gtm-json-converter)

Google Tag Manager がエクスポートした JSON をエクセルで開ける CSV に変換します

1 行に 1 つのタグ、列は以下を出力します

1. ID (GTM 内部で使われている識別子)
2. タグ名
3. タグ
4. document.write フラグ (カスタム HTML の場合)
5. トリガー

## 使い方

clone してためす場合

```bash
$ cd gtm-json-converter
$ npm i
$ npm start gtm.json # JSON のパスを渡す
```

グローバルインストールする場合

```bash
$ npm i -g @opt-tech/gtm-json-converter
$ gtm-json-converter gtm.json # JSON のパスを渡す
```

カレントディレクトリの `[コンテナ名] エクスポート日時.csv` に保存されます
npm package: @opt/nopt
Description: Plugin for @opt/parse making nopt the parser
Author: Eli Doran
Latest version: 0.1.1

# @opt/nopt
[![Build Status](https://travis-ci.org/elidoran/node-opt-nopt.svg?branch=master)](https://travis-ci.org/elidoran/node-opt-nopt)
[![Dependency Status](https://gemnasium.com/elidoran/node-opt-nopt.png)](https://gemnasium.com/elidoran/node-opt-nopt)
[![npm version](https://badge.fury.io/js/%40opt%2Fnopt.svg)](http://badge.fury.io/js/%40opt%2Fnopt)
[![Coverage Status](https://coveralls.io/repos/github/elidoran/node-opt-nopt/badge.svg?branch=master)](https://coveralls.io/github/elidoran/node-opt-nopt?branch=master)

Plugin for @opt/parse making nopt the parser.

See [@opt/parse](https://www.npmjs.com/package/@opt/parse)

See [@opt/nopt](https://www.npmjs.com/package/nopt)

See [@use/core](https://www.npmjs.com/package/@use/core)


## Install

```sh
npm install @opt/nopt --save
```


## Usage

```javascript
var parse = require('@opt/parse')

// choose the internal parser as `nopt`
parse.use('@opt/nopt')

// optionally add other plugins by package name:
parse.use('@opt/words', '@opt/require')

// then use parse as you would use `nopt`,
// plus any changes made possible by the plugins added
options = parse({}, {}, process.argv, 2)
```


## MIT License
npm package: @opt/parse
Description: Modular options parser allowing plugins to provide everything.
Author: Eli Doran
Latest version: 0.2.0

# @opt/parse
[![Build Status](https://travis-ci.org/elidoran/node-opt-parse.svg?branch=master)](https://travis-ci.org/elidoran/node-opt-parse)
[![Dependency Status](https://gemnasium.com/elidoran/node-opt-parse.png)](https://gemnasium.com/elidoran/node-opt-parse)
[![npm version](https://badge.fury.io/js/%40opt%2Fparse.svg)](http://badge.fury.io/js/%40opt%2Fparse)
[![Coverage Status](https://coveralls.io/repos/github/elidoran/node-opt-parse/badge.svg?branch=master)](https://coveralls.io/github/elidoran/node-opt-parse?branch=master)

Modular options parser allowing plugins to provide everything.

This package doesn't do parsing, it provides the target for plugins to add their stuff.

The expectations are:

1. You will use plugins. If you weren't, you'd just `require()` your favorite parser.
2. So, you will call `parse.use()` at least once to load at least one plugin.
3. So, you can specify the plugin providing the options parser as the first param, like: `parser.use('some-parser-plugin', 'another-plugin')`. For example, use `@opt/nopt` to use `nopt` to parse.

The above expectations mean this package doesn't do parsing itself. It has no dependency on a parser package. So, no baggage when requiring different parsers.


## Install

```sh
npm install @opt/parse --save
```


## Usage

```javascript
var parse = require('@opt/parse')

// Must provide a plugin with parse implementation. This uses @opt/nopt.
// other plugins are optional. May specify them in separate use() calls.
parse.use('@opt/nopt', '@opt/words', '@opt/require')

// then use parse as you would use `nopt`,
// plus any changes made possible by the plugins added
options = parse({}, {}, process.argv, 2)
```


## Usage: Plugins

See [@use/core](https://www.npmjs.com/package/@use/core) to understand how the `use()` function behaves.

See real plugins:

1. [@opt/nopt](https://www.npmjs.com/package/@opt/nopt)
2. [@opt/words](https://www.npmjs.com/package/@opt/words)
3. [@opt/require](https://www.npmjs.com/package/@opt/require)

TODO: Make a plugin to handle type def stuff. It could be parser implementation agnostic. Then, the parser implementation plugins could grab all additional type defs from a standard format.

Example of writing a plugin for **@opt/parse**:

```javascript
module.exports = function (options, opt) {
  // use `options` to help configure what you're going to do
  // change `nopt` for your plugin's interests...
  // for example, add to typeDefs like @opt/words does:
  var nopt = require('nopt')

  nopt.typeDefs.someNewType = {
    type: theTypeKey, // used in options spec
    validate: function validateThisType(data, key, value) {
      // either return false for invalid
      // or, return true and optionally change data[key]
    }
  }
}
```


## MIT License
npm package: @opt/require
Description: Plugin for @opt/parse adding type def which calls require() on the value.
Author: Eli Doran
Latest version: 0.2.0

# @opt/require
[![Build Status](https://travis-ci.org/elidoran/node-opt-require.svg?branch=master)](https://travis-ci.org/elidoran/node-opt-require)
[![Dependency Status](https://gemnasium.com/elidoran/node-opt-require.png)](https://gemnasium.com/elidoran/node-opt-require)
[![npm version](https://badge.fury.io/js/%40opt%2Frequire.svg)](http://badge.fury.io/js/%40opt%2Frequire)
[![Coverage Status](https://coveralls.io/repos/github/elidoran/node-opt-require/badge.svg?branch=master)](https://coveralls.io/github/elidoran/node-opt-require?branch=master)

Plugin for @opt/parse adding type def which calls require() on the value.

It adds to nopt's `typeDef` a new type marked by the string `require`. When an option has that type it is tested as a path first, then, `require()` is called on it to get the result, which is placed into the parsed options.

Basically, you can do an option like: `name: require` and `name: [require, Array]` and you'll get back the result of the require operation in the `name` property.

See [@opt/parse](https://www.npmjs.com/package/@opt/parse)

See [@opt/nopt](https://www.npmjs.com/package/nopt)

See [@use/core](https://www.npmjs.com/package/@use/core)


## Install

```sh
npm install @opt/require --save
```


## Usage

```javascript
var parse = require('@opt/parse')

// make nopt the parser and apply our require plugin
parse.use('@opt/nopt', '@opt/require')

var options = {
  // the type def is marked with string 'require()'
  // this allows multiple of them, set into an array.
  plugin: [require, Array]
}

// an example args array with a plugin option to require()
// the module path must be absolute, or relative to CWD. or use ~/
var argv = [ 'node', 'some.js', '--plugin', 'some/module' ]

// then use parse as you would use `nopt`,
// plus any changes made possible by the plugins added
options = parse(options, {}, argv, 2)

// the above would produce:
options = {
  // can't write a function... so, 'theModuleFunction' means a real function
  // returned by require('some/module')
  plugin: [ theModuleFunction ]
  argv: {
    original: [ 'node', 'some.js', '--plugin', 'some/module' ]
    original: [ 'node', 'some.js', '--plugin', 'some/module' ]
    remain  : []
  }
}
```


## MIT License
npm package: @opt/words
Description: Plugin for @opt/parse allowing words to be options for nopt
Author: Eli Doran
Latest version: 0.1.0

# @opt/words
[![Build Status](https://travis-ci.org/elidoran/node-opt-words.svg?branch=master)](https://travis-ci.org/elidoran/node-opt-words)
[![Dependency Status](https://gemnasium.com/elidoran/node-opt-words.png)](https://gemnasium.com/elidoran/node-opt-words)
[![npm version](https://badge.fury.io/js/%40opt%2Fwords.svg)](http://badge.fury.io/js/%40opt%2Fwords)
[![Coverage Status](https://coveralls.io/repos/github/elidoran/node-opt-words/badge.svg?branch=master)](https://coveralls.io/github/elidoran/node-opt-words?branch=master)

Plugin for @opt/parse allowing words to be options for nopt.

See [@opt/parse](https://www.npmjs.com/package/@opt/parse)

See [@opt/nopt](https://www.npmjs.com/package/nopt)

See [@use/core](https://www.npmjs.com/package/@use/core)


## Install

```sh
npm install @opt/words --save
```


## Usage

```javascript
var parse = require('@opt/parse')

// make nopt the parser and apply our words plugin
parse.use('@opt/nopt', '@opt/words')

var options = {
  file: [String, Array] // accept multiple strings
}

var aliases = {
  // normal alias stuff for nopt still applies.
  // these are what's after the prefix '-' or '--'.
  f: '--file', // an example

  // here's what this plugin handles.
  $words: {
    // everything here is a whole word, not prefixed with anything.
    file: '--file'
  }
}

// an example args array
var argv = [ 'node', 'some.js', 'file', 'some/file.js' ]

// then use parse as you would use `nopt`,
// plus any changes made possible by the plugins added
options = parse(options, aliases, argv, 2)

// the above would produce:
options = {
  file: [ 'some/file.js' ],
  argv: {
    original: [ 'node', 'some.js', 'file', 'some/file.js' ]
    cooked  : [ 'node', 'some.js', '--file', 'some/file.js' ]
    remain  : []
  }
}

// nopt would have had no `file` values and remain would be:
// [ 'file', 'some/file.js' ]
```


## MIT License