open-index/open-npm huggingface dataset:
npm package: @royportas/logging
Description: A logging package
Author: Roy Portas
Latest version: 1.0.8

# Logging
[![Build Status](https://travis-ci.org/r-portas/logging.svg?branch=master)](https://travis-ci.org/r-portas/logging)
[![Maintainability](https://api.codeclimate.com/v1/badges/bfa746906c5a4ca69a62/maintainability)](https://codeclimate.com/github/r-portas/logging/maintainability)

A logging framework for browsers and node

## How is this different from other logging frameworks?

This framework is designed with the following things in mind:

- Be as simple as possible
- Provide a simple way to log and group particular classes
- Be easy to turn off logs for particular classes

## Design Principles

- Easy to use
- Works in the browser

## Example

```ts
import { Logger, RootLogger } from "@royportas/logging";

const root = RootLogger();

class MyClass {
    
    logger: Logger;

    constructor() {
        super();
        this.logger = root.getLogger(this.constructor.name);
    }

    somethingHappened() {
        this.logger.debug("A thing happened");
    }
}
```

See the `example` folder for more usage examples.

## Deploying and publishing

The script `yarn deploy` handles publishing new
versions to NPM and pushing the docs to Github pages
npm package: @royriojas/get-exports-from-file
Description: parses a javascript file and outputs a list of exports
Author: capajj@gmail.com
Latest version: 1.4.1

## get-exports-from-file

just a function used by [vscode-exports-autocomplete](https://github.com/capaj/vscode-exports-autocomplete)

api is straighforward:
```javascript
import getExportsFromFile from './index'
// make sure to use absolute paths, not relative paths
getExportsFromFile.es6('/some-js-file.js').then((result) = {
    result.exportsFromFile // array of objects, each object has a String `name` and Boolean `default` props
})
// second argument is a flag to signify you want to attempt to get CommonJS export
getExportsFromFile.cjs('/CJS.js', true).then((result) = {
    result.exportsFromFile // array of objects, each object has a String `name` and Boolean `default` props
})


```
npm package: @roysung/cz-jira-smart-emoji
Description: Forked from moogsG/cz-jira-smart-emoji. Commitizen adapter formatting commit messages using emojis with jira smart commits
Author: RoySung
Latest version: 1.0.4

# @roysung/cz-jira-smart-emoji

> Commitizen adapter formatting commit messages using emojis and jira smart commits

**@roysung/cz-jira-smart-emoji** allows you to easily use emojis in your commits using [commitizen].

```sh
? Select the type of change you are committing: (Use arrow keys)
❯ feature   🌟  A new feature
  fix       🐞  A bug fix
  docs      📚  Documentation change
  refactor  🎨  A code refactoring change
  chore     🔩  A chore change
```

## Install

**Globally**

```bash
npm install --global @roysung/cz-jira-smart-emoji

# set as default adapter for your projects
echo '{ "path": "@roysung/cz-jira-smart-emoji" }' > ~/.czrc
```

**Locally**

```bash
npm install --save-dev cz-emoji
```

Add this to your `package.json`:

```json
"config": {
  "commitizen": {
    "path": "@roysung/cz-jira-smart-emoji"
  }
}
```

## Usage

```sh
git cz
```

## Customization

By default `@roysung/cz-jira-smart-emoji` comes ready to run out of the box. Uses may vary, so there are a few configuration options to allow fine tuning for project needs.

### How to

Configuring `@roysung/cz-jira-smart-emoji` can be handled in the users home directory (`~/.czrc`) for changes to impact all projects or on a per project basis (`package.json`). Simply add the config property as shown below to the existing object in either of the locations with your settings for override.

```json
{
  "config": {
    "@roysung/cz-jira-smart-emoji": {}
  }
}
```

### Configuration Options

#### Types

By default `@roysung/cz-jira-smart-emoji` comes preconfigured with the [Gitmoji](https://gitmoji.carloscuesta.me/) types.

An [Inquirer.js] choices array:

```json
{
  "config": {
    "@roysung/cz-jira-smart-emoji": {
      "types": [
        {
          "emoji": "🌟",
          "code": ":star2:",
          "description": "A new feature",
          "name": "feature"
        }
      ]
    }
  }
}
```

#### Workflows

An [Inquirer.js] choices array:

```json
{
  "config": {
    "cz-emoji": {
      "workflows": [{"name": "testing", "value":"testing"}]
    }
  }
}
```

## Examples

- <https://github.com/Falieson/TRAM>

[commitizen]: https://github.com/commitizen/cz-cli
[inquirer.js]: https://github.com/SBoudrias/Inquirer.js/
npm package: @royyuan/react-wordcloud-17
Description: Simple React + D3 wordcloud component with powerful features.
Author: Chris Zhou
Latest version: 1.2.9

# ☁️ react-wordcloud

Simple React + D3 wordcloud component with powerful features. Uses the [`d3-cloud`](https://github.com/jasondavies/d3-cloud) layout.

![image](/public/wordcloud.png)

## Install

```sh
npm install react-wordcloud
```

Note that `react-wordcloud` requires `react^16.13.0` as a peer dependency.

## Use

### Simple

```js
import React from 'react';
import ReactWordcloud from 'react-wordcloud';

import 'tippy.js/dist/tippy.css';
import 'tippy.js/animations/scale.css';

const words = [
  {
    text: 'told',
    value: 64,
  },
  {
    text: 'mistake',
    value: 11,
  },
  {
    text: 'thought',
    value: 16,
  },
  {
    text: 'bad',
    value: 17,
  },
]

function SimpleWordcloud() {
  return <ReactWordcloud words={words} />
}
```

By default, `ReactWordcloud` is configured with animated tooltips enabled and requires CSS for styling. Tippy provides base styling in the resources above or you can create your own.

### Kitchen Sink

An example showing various features (callbacks, options, size).

```js
const callbacks = {
  getWordColor: word => word.value > 50 ? "blue" : "red",
  onWordClick: console.log,
  onWordMouseOver: console.log,
  getWordTooltip: word => `${word.text} (${word.value}) [${word.value > 50 ? "good" : "bad"}]`,
}
const options = {
  rotations: 2,
  rotationAngles: [-90, 0],
};
const size = [600, 400];
const words = [...];

function MyWordcloud() {
  return (
    <ReactWordcloud
      callbacks={callbacks}
      options={options}
      size={size}
      words={words}
    />
  );
}
```

## Examples

View all documented examples and gallery of `react-wordcloud` applications at https://react-wordcloud.netlify.com/.

You can also run the examples locally:

```sh
git clone git@github.com:chrisrzhou/react-wordcloud

cd react-wordcloud
npm install && npm run docs
```

### No props

[![Edit react-wordcloud-simple](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/bgov9)

### Responsive

[![Edit react-wordcloud-simple](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/55sb8)

### Configurable Options

[![Edit react-wordcloud-interactive](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/fnk8w)

### Callbacks

[![Edit react-wordcloud-interactive](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/4lecp)

## Wordcloud Generator

Create wordclouds using this wordcloud generator: https://wordcloud-generator.netlify.com/

Features supported:

- Edit and Upload text inputs
- Various NLP features (stopwords, ngrams)
- Wordcloud configurations
- Export/save/share wordclouds

## Contributing

The code is written in `typescript`, linted with `xo`, and built with `microbundle`. Examples and documentations are built with `docz`.

Feel free to contribute by submitting a pull request.
npm package: @rozanovskii/node-red-contrib-wasp-frame
Description: A Node-RED node which convert Waspmote Frame data to JSON
Author: Ilia Rozanovskii
Latest version: 0.0.6

# node-red-contrib-wasp-frame

Parse frame from Waspmote Frame format into JSON. ASCII format is supported.

Parse frame from Waspmote Frame format into JSON object. ASCII format is supported. (not BINARY)

This wasp-frame node parse input `msg['payload']` buffer from WaspFrame format into JSON format. Currently version Waspmote v15 is supported.

WaspFrame is formatted frames created with a library included within Waspmote API. See [online documentation](https://development.libelium.com/data-frame-programming-guide/) for more information.

THIS IS NOT READY FOR PRODUCTION YET!

## Input

`payload` object | string

WaspFrame buffer (preferred) or string to parse

#### NOTES:  
Input string example

```
<=>†•#1A2B3C4D1A2B3C4D#NB_IOT_TCP#0#EV_A:0#EV_C:0#EV_D:0#WF:0.000#BAT:65#TIME:23-39-3#DATE:21-1-29#
```

## Output

`payload` object

The parsing result is JSON object. Doublicate properties have sequence number at the end ( ex. `WF`, `WF_1`, `WF_2` ).

### Output format "Flat JSON (key/value)"

Output examle  

```
{
	"frametype":"Information",
	"SerialID":"1A2B3C4D1A2B3C4D",
	"WaspmoteID":"NB_IOT_TCP",
	"Sequence":0,
	"EV_A":0,
	"EV_C":0,
	"EV_D":0,
	"WF":0,
	"BAT":65,
	"TST":1652954095
}
```


### Output format "InfluxDB 1.8 ready"

Output examle  

```
[
	{
	"EV_A":0,
	"EV_C":0,
	"EV_D":0,
	"WF":0,
	"BAT":65
	},
	{
	"frametype":"Information",
	"SerialID":"1A2B3C4D1A2B3C4D",
	"WaspmoteID":"NB_IOT_TCP",
	"Sequence":0
	}
]
```


### Output format "InfluxDB 2.0 ready"

Output examle  

```
{
   "bucket":"MyBucket",
   "data":[
      {
		 measurement:"MyMeasurement",
         "tags":{
			"frametype":"Information",
            "SerialID":"1A2B3C4D1A2B3C4D",
            "WaspmoteID":"NB_IOT_TCP",
            "Sequence":0
         },
         "fields":{
            "EV_A":0,
            "EV_C":0,
            "EV_D":0,
            "WF":0,
            "BAT":65
         },
         "timestamp":"2021-01-29T21:39:03.000Z"
      }
   ]
}
```

Frame field `frame.addTimestamp()` (`TST`) transforms into `timestamp` property.