open-index/open-npm huggingface dataset:
npm package: @rreichelt/pw-gen
Description: A simple password generating module with a CLI
Author: Raffael Reichelt
Latest version: 1.0.3

# password-generator
password-generator is a tool to generate passwords from commandline or as a library.

## install
```npm install password-generator```

## usage
password-generator [options]
Without Options it woll generate a password with lowercase letters and numbers grouped by 4 letters and seperated with a *-* with a length of 14.

````
Options:
  --help           Hilfe anzeigen                                      [boolean]
  --version        Version anzeigen                                    [boolean]
  -m, --max        Set password length                                    [Zahl]
  -t, --tupel      Set group length                                       [Zahl]
  -s, --seperator  set group seperator - 0 for none                       [Zahl]
  -l, --lowercase  Include lowercase letters          [boolean] [Standard: true]
  -u, --uppercase  include upercase letters          [boolean] [Standard: false]
  -n, --numbers    Include numbers                    [boolean] [Standard: true]
  -x, --specials   Include special letters           [boolean] [Standard: false]
  ```
npm package: @rrelmy/vue-cli-plugin-storybook
Description: Vue CLI plugin for Storybook
Author: Pavan Kumar Sunkara
Latest version: 3.0.1

# vue-cli-plugin-storybook

Vue CLI plugin for Storybook

## Installation

```
$ vue add storybook
```

<p align=center><img src=screencast.svg width=600></p>

## Usage

It will create a config folder for storybook, a sample component and a sample story. The webpack config used for storybook is resolved from `vue-cli-service`, which means you don't need to have any special `webpack` section in storybook config folder.

However, storybook will filter all the plugins for webpack according to internal list of allowed plugins. If you are extending your config with your custom plugins, you can extend list of allowed plugins by passing their names through `pluginOptions` in your `vue.config.js` like this:

```js
{
  pluginOptions: {
    storybook: {
      allowedPlugins: [
        'define'
      ]
    }
  }
}
```

The name of the plugin is the string used in webpack-chains `config.plugin(...)` call.

Note that only plugins defined with [webpack-chain](https://cli.vuejs.org/guide/webpack.html#chaining-advanced) config can be filtered using the `allowedPlugins` option. Plugings defined through `configureWebpack` will always be included in the final webpack config.

## Contributors
Here is a list of [Contributors](http://github.com/storybookjs/vue-cli-plugin-storybook/contributors)

We particularly thank `Almas Akchabayev <almas.akchabayev@gmail.com>` for the initial code and willing to transfer the project to us.

### TODO

__I accept pull requests and guarantee a reply back within a day__

## License
MIT/X11

## Bug Reports
Report [here](http://github.com/storybookjs/vue-cli-plugin-storybook/issues). __Guaranteed reply within a day__.

## Contact
Pavan Kumar Sunkara (pavan.sss1991@gmail.com)

Follow me on [github](https://github.com/users/follow?target=pksunkara), [twitter](http://twitter.com/pksunkara)
npm package: @rremer/editjs
Description: JavaScript editor
Author: Richard Remer
Latest version: 0.1.0

EditJS is a JavaScript code editor based on CodeMirror.

Installing
==========

Clone Repository
----------------
```sh
git clone git@github.com:richRemer/editjs.git
```

Navigate to Repository
----------------------
```sh
cd editjs
```

Build Using make
----------------
```sh
make
```

Install Using make
------------------
```
sudo make install
```

Uninstalling
============
Navigate to Repository
----------------------
```sh
cd editjs
```

Uninstall Using make
--------------------
```sh
sudo make uninstall
```
npm package: @rrequire/client
Description: rrequire client for browser environments
Author: Mike Shi
Latest version: 0.0.6

See full documentation in the repo: https://github.com/MikeShi42/rrequire

![rrequire logo](https://i.imgur.com/0zexI83.png)

# why rrequire?

The 🚀 fastest ⚡️ way for web apps to start talking to servers.
Connect your frontend to your backend with just 3 lines of code and
zero configuration.

Enjoy familiar node module export syntax
and ES6 import syntax to make your remote calls.

**Warning**: This package is still experimental and the API may change
in-between minor versions.

## Getting Started

### Web Client

The `rrequire` client allows for easy calls from a web browser
to a remote server implementing the `JSON-RPC` protocol (such as the
`@rrequire/server`).

#### Install from npm:

    npm install @rrequire/client

#### 'Import' a remote function for use:

    import rrequire from '@rrequire/client';

    const { add } = rrequire('server/module');

    async function myClientMethod(x) {
      console.log(await add(x, 5));
    }

By default, `rrequire` will try to send requests to the current host (`/`).

All functions return
[`Promises`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises)
that will resolve to the value that's returned
by the remote procedure (or reject if a problem occurs). It's recommended
to use the [`async/await`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function)
syntax for more concise code.

Note: As of this time, module names are not used to scope function imports.

#### Configuration

Import the config function to globally set configs for future RPC requests.

    import rrequire, { config } from '@rrequire/client';

    config({ remoteLocation: 'http://localhost:8080' });

**Config Options**

Key | Type | Default | Description
--- | --- | --- | ---
`remoteLocation` | `String` | `/` | URL of the `JSON-RPC` server.

#### Advanced Usage: Avoiding ES6 Proxy

The usage of
[`Proxy`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy)
in production can cause problems for browsers that
do not yet support `Proxy`. The `Proxy` object is used to magically catch
all property references at run time (ex. module.function),
allowing for easy ES6-like import syntax and minimal overhead. Since
there is no polyfill for `Proxy`, you must
instead explicitly define which functions you expect to import from
the remote server.

By passing in an array of function names into the `rrequire` function call,
`rrequire` avoids using `Proxy` and creates a static object with all functions
pre-defined according to the array.

**Example**

    const {
        add,
        subtract,
    } = rrequire('server/module', [
        // This array specifies which function names we're importing
        // It should match the above properties
        'add',
        'subtract',
    ]);
npm package: @rrequire/server
Description: rrequire RPC server for node environments
Latest version: 0.0.6

See full documentation in the repo: https://github.com/MikeShi42/rrequire

![rrequire logo](https://i.imgur.com/0zexI83.png)

# why rrequire?

The 🚀 fastest ⚡️ way for web apps to start talking to servers.
Connect your frontend to your backend with just 3 lines of code and
zero configuration.

Enjoy familiar node module export syntax
and ES6 import syntax to make your remote calls.

**Warning**: This package is still experimental and the API may change
in-between minor versions.

# Getting Started

## Server

The `rrequire` server allows for easy definition of remote functions
that will be served on a Node server using the `JSON-RPC` protocol over
http.

### Install from npm:

    npm install @rrequire/server

### 'Export' a remote function:

    function add(x, y) {
      return x + y;
    }

    require('@rrequire/server').serve({
      add,
    });

Using `serve` a `rrequire` server on port 8080 will be started with CORS
enabled for any host for quick prototyping.

### Stand-Alone Configuration

Call the `start` function before any `export` function calls
to explicitly start the Node server with custom options. Calling `start`
after an `export` will have no effect.

Calling `serve` alone will automatically start up a server with default
options.

    const rrequire = require('@rrequire/server')

    // ...function definitions here

    rrequire.start({ port: 3000, enableCors: true });
    rrequire.export({
      // ... function exports here
    });


**Function Signature**: `export(Object functionsToExport)`

Export with Options Example:

    require('@rrequire/server').export({
        func1,
        func2,
    });

**Start Options**

Key | Type | Default | Description
--- | --- | --- | ---
`port` | `Number` | `3000` | Port number to listen to incoming RPC requests.
`enableCors` | `Boolean` | `true` | If true, allows RPC requests from any domain.

### Connect Middleware (Use in Existing Apps)

Use rrequire in your current express/connect app by inserting the rrequire
server as middleware.

```
const rrequire = require('@rrequire/server');
const express = require('express');

const app = express();
// ... Your express app
app.all('/rpc', rrequire.middleware({ enableCors: true }));
```

**Middleware Options**

Key | Type | Default | Description
--- | --- | --- | ---
`end` | `Boolean` | `true` | If set to `false` causes the middleware to `next()` instead of `res.end()` when finished.
`enableCors` | `Boolean` | `true` | If true, allows requests from any domain.

#### Further Info

The server largely depends on [`jayson`](https://github.com/tedeh/jayson)
middleware to handle RPC function registration and invocation.
iddleware to handle RPC function registration and invocation.
npm package: @rreusser/regl-camera
Description: Camera for regl
Author: Mikola Lysenko
Latest version: 1.1.0
Deprecated: @rreusser/regl-camera is deprecated since fixes have been merged upstream into https://www.npmjs.com/package/regl-camera

# @rreusser/regl-camera
A basic reusable "turntable" camera component for [regl](http://regl.party).  (Secretly just [spherical coordinates](https://en.wikipedia.org/wiki/Spherical_coordinate_system).)


## THIS FORK

***Is a fork of `regl-camera` published separately at @rreusser/regl-camera.***

## Example

```javascript
const regl = require('regl')()
const camera = require('regl-camera')(regl, {
  center: [0, 2.5, 0]
})

const bunny = require('bunny')
const normals = require('angle-normals')

const drawBunny = regl({
  frag: `
    precision mediump float;
    varying vec3 vnormal;
    void main () {
      gl_FragColor = vec4(abs(vnormal), 1.0);
    }`,
  vert: `
    precision mediump float;
    uniform mat4 projection, view;
    attribute vec3 position, normal;
    varying vec3 vnormal;
    void main () {
      vnormal = normal;
      gl_Position = projection * view * vec4(position, 1.0);
    }`,
  attributes: {
    position: bunny.positions,
    normal: normals(bunny.cells, bunny.positions)
  },
  elements: bunny.cells
})

regl.frame(() => {
  regl.clear({
    color: [0, 0, 0, 1]
  })
  camera(() => {
    drawBunny()
  })
})
```

## Install

```
npm i regl-camera
```

## API

### Constructor

#### `var camera = require('regl-camera')(regl[, options])`
`module.exports` of `regl-camera` is a constructor for the camera.  It takes the following arguments:

* `regl` is a handle to the regl instance
* `options` is an object with the following optional properties:
  + `center` which is the center of the camera
  + `theta` the theta angle for the camera
  + `phi` the phi angle for the camera
  + `distance` the distance from the camera eye to the center
  + `up` the up vector for the camera
  + `mouse` set to `false` to turn off mouse events
  + `damping` multiplier for inertial damping (default 0.9). Set to 0 to disable inertia.

### Command usage

#### `camera(block)`
`regl-camera` sets up an environment with the following variables in both the context and uniform blocks:

| Variable | Type | Description |
|----------|------|-------------|
| `view`   | `mat4` | The view matrix for the camera |
| `projection` | `mat4` | The projection matrix for the camera |
| `center` | `vec3` | The center of the camera |
| `eye` | `vec3` | The eye coordinates of the camera |
| `up` | `vec3` | The up vector for the camera matrix |
| `theta` | `float` | Latitude angle parameter in radians |
| `phi` | `float` | Longitude angle parameter in radians |
| `distance` | `float` | Distance from camera to center of objective |

**Note**
These properties can also be accessed and modified directly by accessing the object

## License
(c) 2016 Mikola Lysenko. MIT License
npm package: @rreyna/react-tracker-canvas
Description: react-tracker-canvas React component
Author: Raphael Reyna
Latest version: 1.6.2

# react-tracker-canvas

Tracks the mouse over a canvas element with some nice animations.
Can handle mapping the canvas onto arbitrary rectangular regions in the plane.

[Read the documentation](https://raphaelreyna.works/react-tracker-canvas/)

## Installation
` npm i @rreyna/react-tracker-canvas `
npm package: @rrishabh/ui
Description: A simple UI library
Author: Rishabh Sharma
Latest version: 9.7.9

# TileChart Component

The `TileChart` is a React component that displays data in a tile format, where each tile represents a day. The color of the tile indicates the status of that day, which can be "success", "warning", or "alert".

## Props

- `data`: An array of objects, where each object represents a day and has a `date` and a `status`. The `date` is a string in ISO format, and the `status` can be "success", "warning", or "alert".
- `range`: The number of months to display. It can be 3, 6, or 12. The default is 6.
- `onTileHover`: A callback function that is called when a tile is hovered over. It receives the date and status of the hovered tile.
- `tileText`: A string that is displayed on each tile.

## Usage

```tsx
import TileChart from './TileChart';

const data = [
  { date: '2022-01-01T00:00:00.000Z', status: 'success' },
  { date: '2022-01-02T00:00:00.000Z', status: 'warning' },
  // More data...
];

function App() {
  return (
    <TileChart
      data={data}
      range={6}
      onTileHover={(date, status) => console.log(date, status)}
      tileText="Day"
    />
  );
}

export default App;
npm package: @rrlopez/overlay-manager
Description: Overlay Manager for React is a lightweight and flexible library designed to simplify the management of overlays (modals, toasts, drawers, etc.) in React applications. It provides a straightforward API for creating, showing, hiding, and managing overlays w
Author: Ricardo Rey Crisanto V. Lopez II
Latest version: 1.0.0

# Overlay Manager for React

## Overview

Overlay Manager for React is a lightweight and flexible library designed to simplify the management of overlays (modals, toasts, drawers, etc.) in React applications. It provides a straightforward API for creating, showing, hiding, and managing overlays within your React components.

## Features

-**Easy Integration:** Seamlessly integrate overlay functionality into your React components with minimal setup.
-**Flexible Configuration:** Customize overlay behavior, and interactions to suit your application's needs.
-**Support for Various Overlay Types:** Manage modals, toasts, drawers, and more with ease.
-**Event Handling:** Handle overlay events such as opening, closing, and interactions efficiently.
-**Accessibility:** Ensure accessibility standards are met by providing built-in support for keyboard navigation and screen readers.
-**Lightweight:** Keep your application lightweight by using a minimal and optimized library for overlay management.

## Installation

You can install Overlay Manager for React via npm or yarn:

```bash
npm install @rrlopez/overlay-manager
# or
yarn add @rrlopez/overlay-manager
```

## Usage

To use Overlay Manager for React, simply import the necessary components and integrate them into your React application:

```jsx
import { OverlayManager, addOverlay} from '@rrlopez/overlay-manager';

const MyComponent = () => {
  const handleClick = () => {
    addOverlay(YourModalComponent);
  };

  return (
    <div className="w-screen h-screen flex items-center justify-center">
      <button className="btn btn-primary btn-bordered" onClick={handleClick}>
        Click Me
      </button>
    </div>
  );
};

function YourModalComponent({open, onClose}: {open: boolean, onClose: ()=>null}) {

  return (
    <Modal defaultOpen={open} onOpenChange={onClose}>
	    // content of your modal
    </Modal>
  );
}

const App = () => {
  return (
    <>
      <OverlayManager />
      <MyComponent />
    </>
  );
};

export default App;
```
npm package: @rrnara/react-devise
Description: A react front-end for a ruby on rails devise authentication server.
Author: Tim Scott
Latest version: 0.1.2

**ATTENTON**: Forked repo

# React Devise

## Introduction

Devise has long been the go-to authentication library for Rails apps. Just drop Devise into your Rails app, make a few tweaks, and get on with building awesome business features. 

Much of Devise's functionality involves server side routing and rendering, so what about single page apps? Does Devise do that, or must you leave Devise behind when you move to React? Maybe not. It turns out it's pretty easy to purpose Devise as an authentication backend. 

But that leaves undone a bunch of routing and view related functionality that Devise provides out of the box.

Enter **React Devise**.

The goal of React Devise is to make it extremely easy to add authentication to a new React+Rails app while maintaining the total flexibility that Devise users have come to expect.

## Dependencies

React Devise has deep dependencies on a few popular React modules. The most significant are:

* [react-redux](https://github.com/reactjs/react-redux)
* [react-router](https://github.com/ReactTraining/react-router)
* [redux-form](https://github.com/erikras/redux-form)

If you don't want to use these in your app, React Devise is probably not for you.

## Installation

```
yarn add @rrnara/react-devise
```

## Documentation

[Documenation Wiki](https://github.com/timscott/react-devise/wiki/Home)

## Reference App

Have a look at a reference implementation.

* [The code](https://github.com/timscott/react-devise-sample)
* [Demo on Heroku](http://react-devise-sample.herokuapp.com/)

## To Do

* Create a ruby gem
* Ouath support
* Support multiple resource types
* Support all devise views
* Support more customization of messages
* Possibly an "eject" function to allow full customization of views
* ???
npm package: @rrov1/iobroker.epson_workforce
Description: Ink status of Epson Workforce printers
Author: rrov1
Latest version: 0.0.2

![Logo](admin/epson_stylus_px830.png)
# ioBroker.epson_workforce

![Number of Installations](http://iobroker.live/badges/epson_workforce-installed.svg) ![Number of Installations](http://iobroker.live/badges/epson_workforce-stable.svg) [![NPM version](http://img.shields.io/npm/v/iobroker.epson_workforce.svg)](https://www.npmjs.com/package/iobroker.epson_workforce)
[![Downloads](https://img.shields.io/npm/dm/iobroker.epson_workforce.svg)](https://www.npmjs.com/package/iobroker.epson_workforce)

[![NPM](https://nodei.co/npm/iobroker.epson_workforce.png?downloads=true)](https://nodei.co/npm/iobroker.epson_workforce/)


:de: [Dokumentation](/docs/de/doc_epson_workforce_de.md)

:uk: [Documentation](/docs/en/doc_epson_workforce_en.md)


## Changelog
### 0.0.1 (2020-08-30)
* (rrov1) forked from iobroker.epson_stylus_px830 0.2.1

## ToDo
* Nicer icon !
* ioBroker.Discovery support
* Take Screenshots in different languages

## License

The MIT License (MIT)

Copyright (c) 2020 rrov1

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

---
*Dank an die Erfinder des Basisskripts zum Parsen der Daten, Idittmar und MistyReblaus aus dem [Homematic-Forum](http://homematic-forum.de/forum/viewtopic.php?f=31&t=25140).* :+1: 

*Dank an pix für die Vorlage
npm package: @rrpm/netlify-cms
Description: An extensible, open source, Git-based, React CMS for static sites.
Latest version: 2.2.47

# Netlify CMS
[![](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/netlify/netlifycms)

A CMS for static site generators. Give non-technical users a simple way to edit
and add content to any site built with a static site generator.

## How it works

Netlify CMS is a single-page app that you pull into the `/admin` part of your site.

It presents a clean UI for editing content stored in a Git repository.

You setup a YAML config to describe the content model of your site, and typically
tweak the main layout of the CMS a bit to fit your own site.

When a user navigates to `/admin/` they'll be prompted to login, and once authenticated
they'll be able to create new content or edit existing content.

Read more about Netlify CMS [Core Concepts](https://www.netlifycms.org/docs/intro/).

# Installation and Configuration

The Netlify CMS can be used in two different ways.

* A Quick and easy install, that just requires you to create a single HTML file and a configuration file. All the CMS Javascript and CSS are loaded from a CDN.
  To learn more about this installation method, refer to the [Quick Start Guide](https://www.netlifycms.org/docs/quick-start/)
* A complete, more complex install, that gives you more flexibility but requires that you use a static site builder with a build system that supports npm packages.

# Community

Netlify CMS has a [Gitter community](https://gitter.im/netlify/netlifycms) where members of the community hang out and share things about the project, as well as give and receive support.

# Contributing

New contributors are always welcome! Check out [CONTRIBUTING.md](https://github.com/netlify/netlify-cms/blob/master/CONTRIBUTING.md) to get involved.

# Change Log

This project adheres to [Semantic Versioning](http://semver.org/).
Every release is documented on the Github [Releases](https://github.com/netlify/netlify-cms/releases) page.

# License

Netlify CMS is released under the [MIT License](LICENSE).
Please make sure you understand its [implications and guarantees](https://writing.kemitchell.com/2016/09/21/MIT-License-Line-by-Line.html).

# Thanks

## Services
These services support Netlify CMS development by providing free infrastructure.
<p>
  <a href="https://www.travis-ci.org">
    <img src="https://raw.githubusercontent.com/netlify/netlify-cms/master/img/travis.png" height="38"/>
  </a>
  <img src="https://spacergif.org/spacer.gif" width="20"/>
  <a href="https://www.browserstack.com">
    <img src="https://raw.githubusercontent.com/netlify/netlify-cms/master/img/browserstack.png" height="38"/>
  </a>
</p>
npm package: @rrpm/netlify-cms-backend-bitbucket
Description: Bitbucket backend for Netlify CMS
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-backend-bitbucket/README.md)!
npm package: @rrpm/netlify-cms-backend-git-gateway
Description: Git Gateway backend for Netlify CMS
Latest version: 2.1.15

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-backend-git-gateway/README.md)!
npm package: @rrpm/netlify-cms-backend-github
Description: GitHub backend for Netlify CMS
Latest version: 2.1.10

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-backend-github/README.md)!
npm package: @rrpm/netlify-cms-backend-gitlab
Description: GitLab backend for Netlify CMS
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-backend-gitlab/README.md)!
npm package: @rrpm/netlify-cms-backend-test
Description: Development testing backend for Netlify CMS
Latest version: 2.0.8

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-backend-test/README.md)!
npm package: @rrpm/netlify-cms-core
Description: Netlify CMS core application, see netlify-cms package for the main distribution.
Latest version: 2.2.38

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-core/README.md)!
npm package: @rrpm/netlify-cms-editor-component-image
Description: Image component for Netlify CMS editor widget
Latest version: 2.0.6

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-editor-component-image/README.md)!
npm package: @rrpm/netlify-cms-lib-auth
Description: Shared authentication functionality for Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-lib-auth/README.md)!
npm package: @rrpm/netlify-cms-lib-util
Description: Shared utilities for Netlify CMS.
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-lib-util/README.md)!
npm package: @rrpm/netlify-cms-media-library-uploadcare
Description: Uploadcare integration for Netlify CMS
Latest version: 0.2.3

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-media-library-uploadcare/README.md)!
npm package: @rrpm/netlify-cms-ui-default
Description: Default UI components for Netlify CMS.
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-ui-default/README.md)!
npm package: @rrpm/netlify-cms-widget-boolean
Description: Widget for editing boolean values in Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-boolean/README.md)!
npm package: @rrpm/netlify-cms-widget-date
Description: Widget for editing dates in Netlify CMS.
Latest version: 2.0.8

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-date/README.md)!
npm package: @rrpm/netlify-cms-widget-datetime
Description: Widget for editing dates and times in Netlify CMS.
Latest version: 2.0.8

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-datetime/README.md)!
npm package: @rrpm/netlify-cms-widget-file
Description: Widget for uploading files in Netlify CMS.
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-file/README.md)!
npm package: @rrpm/netlify-cms-widget-image
Description: Widget for uploading images in Netlify CMS.
Latest version: 2.1.2

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-image/README.md)!
npm package: @rrpm/netlify-cms-widget-list
Description: Widget for editing lists in Netlify CMS.
Latest version: 2.0.9

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-list/README.md)!
npm package: @rrpm/netlify-cms-widget-markdown
Description: Widget for editing markdown in Netlify CMS.
Latest version: 2.0.11

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-markdown/README.md)!
npm package: @rrpm/netlify-cms-widget-number
Description: Widget for editing numberic values in Netlify CMS.
Latest version: 2.0.8

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-number/README.md)!
npm package: @rrpm/netlify-cms-widget-object
Description: Widget for displaying an object of fields for Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-object/README.md)!
npm package: @rrpm/netlify-cms-widget-relation
Description: Widget for linking related entries in Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-relation/README.md)!
npm package: @rrpm/netlify-cms-widget-select
Description: Selectable values widget for Netlify CMS.
Latest version: 2.0.6

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-select/README.md)!
npm package: @rrpm/netlify-cms-widget-string
Description: Widget for editing plain string values in Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-string/README.md)!
npm package: @rrpm/netlify-cms-widget-text
Description: Widget for editing multiline plain string values in Netlify CMS.
Latest version: 2.0.7

# Docs coming soon!

Netlify CMS was recently converted from a single npm package to a "monorepo" of over 20 packages.
That's over 20 Readme's! We haven't created one for this package yet, but we will soon.

In the meantime, you can:

1. Check out the [main readme](https://github.com/netlify/netlify-cms/#readme) or the [documentation
   site](https://www.netlifycms.org) for more info.
2. Reach out to the [community chat](https://gitter.im/netlify/netlifycms/) if you need help.
3. Help out and [write the readme yourself](https://github.com/netlify/netlify-cms/edit/master/packages/netlify-cms-widget-text/README.md)!
npm package: @rrrm/countries
Description: a list of countries and cities based on JSON file
Author: Rafael Magalhaes
Latest version: 0.1.0

# Countries and Cities 

This node package provides functions for working with countries and cities data.

## Installation

```bash
pnpm i @rrrm/countries
```

## Usage

- `countries`: An array of countries.
- `cities`: An array of cities.
- `findCountry(countryCode: string, {withCity:false //default})`: Find a country by its country code.
- `findCities(cityName: string, {withCountry:false //default})`: Find cities by name.
- `getAllCitiesByCountry(countryCode: string)`: Get all cities in a specific country.


```javascript

import { findCities, findCountry, getAllCitiesByCountry } from "@rrrm/countries"

// find cities with country information
const bissau = findCities("bissau", { withCountry: true })
console.log("findCities-> ", bissau)

// find a country with all cities
const gw = findCountry("GW", { withCity: true })
console.log("findCountry-> ", gw)

// get all cities for a country
const citiesBycountry = getAllCitiesByCountry("GW")
console.log("getAllCitiesByCountry-> ", citiesBycountry)

```

## Utilities

this is helpful if you want to import the data into your own database.

- `convertJson(fileName: string, data: any | Country[] | City[])`: Convert data to JSON format and save it to a file.
- `convertCSV(fileName: string, data: any | Country[] | City[])`: Convert data to CSV format and save it to a file.


```javascript
import { convertJson, convertCSV } from './convert.ts';

const data = [{ /* Your data here */ }];
convertJson('data.json', data);
convertCSV('data.csv', data);
```

### Data Files

This utility assumes the presence of data files in JSON format. Ensure you have the required data files in the specified locations before using the utility.

- `countries.json`: Country data file.
- `cities.json`: City data file.

There is also csv files of both countries and cities this is to make it easier to import data to any database as the package size is quite large.


### Schema

schema folder will contain sql files so data can be added to a database

## License

This utility is provided under the [MIT License](LICENSE).

## Credits
this package is a comnbination of both [restcountries](https://gitlab.com/restcountries/restcountries) and [cities.json](https://github.com/lutangar/cities.json/tree/master)
npm package: @rrsilaya/scheda
Description: Fork of @ravenjohn's [scheda.js](https://github.com/ravenjohn/scheda.js), rewritten in ES6 syntax. Create SystemOne-inspired schedule timetable!
Author: rrsilaya
Latest version: 1.0.0

# scheda.js
Fork of @ravenjohn's [scheda.js](https://github.com/ravenjohn/scheda.js), rewritten in ES6 syntax. Create SystemOne-inspired schedule timetable!

### Usage
```html
<script src="./dist/scheda.min.js"></script>
<script>
  const scheda = new Scheda();
  scheda.init();

  scheda.add({
    day: 'M',
    time: '8:30-9:45',
    courseCode: 'CMSC 142',
    section: 'UV-4L',
    room: 'Physical Sciences Bldg.',
  });
</script>
```

Make sure to include the canvas element somewhere in your HTML code as `<canvas id="scheda" />`.

### Cases
#### `constructor(config?: Object)`
`Scheda` constructor can accept a configuration object.

```javascript
import Scheda from 'scheda.js';

const config = {
  id: 'my-schedule',                // custom canvas ID
  colors: ['#000000', '#ff0000'],   // array of preset course colors
  theme: {
    background: '#FFFFFF',
    header: '#00838F',
    grid: {
      mini: '#DFE0D2',
      horizontal: '#00838F',
      vertical: '#00838F'
    },

    time: {
      color: '#FFFFFF',
      background: '#00838F',
      style: 'bold',
      font: 'Arial',
      size: 12,
    },
    day: {
      color: '#FFFFFF',
      style: 'bold',
      font: 'Arial',
      size: 12
    },
    sched: {
      color: '#FFFFFF',
      style: 'bold',
      font: 'Arial',
      size: 10
    },

    timeColumnWidth: 80,
  }
}

const scheda = new Scheda(config);
```

#### `scheda.init(canvasElement?: Node)`
Draws initial scheda elements.

```javascript
const scheda = new Scheda();

const canvas = document.querySelector('canvas#mySchedule');
scheda.init(canvas); // can accept a node element

/*
  The above code can be written as:
  const scheda = new Scheda({ id: 'mySchedule' });
  scheda.init();
*/
```

#### `scheda.add(course: Object)`
Adds a course to scheda canvas. Returns the course UUID.

#### `scheda.get(id: String)`
Returns course object from the scheda history given the course UUID.

#### `scheda.remove(id: String)`
Removes course from scheda canvas.

#### `scheda.update(id: String, course: Object)`
Updates course identified by UUID given.

#### `scheda.download(filename?: String)`
Generates a PNG file of the schedule.