open-index/open-npm huggingface dataset:
npm package: @olegivaniv/n8n-nodes-overkiz-tahoma
Description: This is an n8n community node. It lets you use Overkiz (Tahoma) in your n8n workflows.
Author: Oleg Ivaniv
Latest version: 0.1.0

# n8n-nodes-overkiz-tahoma
This is an n8n community node. It lets you use Overkiz (Tahoma) in your n8n workflows.

Overkiz (Tahoma) is a service for home automation that allows you to control various connected objects such as lights, blinds, and more.

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/reference/license/) workflow automation platform.

[Installation](#installation)  
[Operations](#operations)  
[Credentials](#credentials)  <!-- delete if no auth needed -->  
[Compatibility](#compatibility)  
[Resources](#resources)    

## Installation
Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations
The Overkiz (Tahoma) node supports the following operations:

- Get Many: Get many objects
- Get Single: Get a single object
- Get By Type: Get objects by type
- Execute Command: Executes a command on an object

Currently, there are only commands to control shutter blinds (PositionableExteriorVenetianBlind) and lights (DimmerLight, DimmerHueSatOrCTLight, DimmerColorTemperatureLight) because those are the only devices I have available for testing. 

However, contributions are welcome to extend the node with more commands for other devices. 

Please submit a PR if you would like to contribute.

## Credentials
To use the Overkiz (Tahoma) node, you need to authenticate with the Overkiz API. Sign up with Overkiz and obtain your hostname, email, and password. Then, set them up in the Overkiz API credentials in n8n.

## Compatibility
This node has been tested with n8n version 1.1.1. Backward compatibility with other versions is not guaranteed.

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/community-nodes/)
* [Overkiz API library](https://github.com/bbriatte/overkiz-api)
* [Somfy TaHoma local API](https://somfy-developer.github.io/Somfy-TaHoma-Developer-Mode/#/)
npm package: @olegjo/docker-utils
Description: Package to manage docker from a TypeScript or JavaScript based application.
Author: Ole Gunnar Johansen
Latest version: 0.2.0

# TypeScript Docker Utility library

## Docker Compose
This library can be used to programatically create a docker-compose file.

Example:
```TypeScript
import * as Docker from "@olegjo/docker-utils";

// Create networks.
const netExternal = new Docker.Compose.Network("net_external", false);

// Create volumes. Volumes of type "volume" are docker volumes. Volumes of type "bind" are bound to the host file system.
const volDatabase = new Docker.Compose.Volume("db_data", "volume", "");
const volConf  = new Docker.Compose.Volume("conf", "bind", "./conf/");

// Set up services.
const dbService = new Docker.Compose.Service("database", "mongodb");
dbService.restart = "unless-stopped";
dbService.networks = [ netExternal ]; // add networks
dbService.addVolume(volDatabase, "/data/db"); // Add volume and set location inside the container

const nginxService = new Docker.Compose.Service("nginx", "nginx");
nginxService.addPort("80", "80");
nginxService.dependsOn = [ dbService ];
nginxService.restart = "unless-stopped";
nginxService.networks = [ netExternal ];
nginxService.addVolume(volConf, "/var/nginx/conf");

// Finally, compile the compose file. 
// The network and volumes sections are automatically added 
// based on their presence in the added services
const composeFile = new Docker.Compose.ComposeFile("2.3");
composeFile.addService(dbService);
composeFile.addService(nginxService);

const compose = composeFile.toYaml();

```
npm package: @olegjs/jsdom-sync
Description: Synchronous script execution in jsdom
Author: Oleg Gunkin
Latest version: 0.0.3
Deprecated: Not maintained

# jsdom-sync

[![Standard - JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](http://standardjs.com/)

Synchronous script execution in jsdom. Made for unit tests.

By default all script in jsdom are executed in parallel. In some cases, like
unit testing, simplicity is more important than performance. This is a wrapper
around jsdom that feeds all script code as inline `script` tags, ensuring
sequential execution.

```js
const jsdomSync = require('jsdom-sync')
const document = jsdomSync(['a.js', 'b.js'])
const window = document.defaultView
// do stuff
window.close()
```

## Notes

* All files included in `script` tags inside `head`; use [`DOMContentLoaded` event](https://developer.mozilla.org/en-US/docs/Web/Events/DOMContentLoaded).
* If you need speed from jsdom, use the callbacks or promises instead.
npm package: @olegjs/lr-http-server
Description: An HTTP server with livereload included
Author: Manuel Cabral
Latest version: 1.0.0-beta.3

# lr-http-server

**Forked [digisfera/lr-http-server](https://github.com/digisfera/lr-http-server) because it has been abandoned for long time. This is not a production-grade server; however, it meets my development needs perfectly.**

An HTTP server with livereload included. If a file inside the folder being served is changed, added or deleted, the browser will automatically reload.

## Installing

    npm install @olegjs/lr-http-server

## Usage

    lr-http-server [-p <port>] [-d <dir>] [-l livereloadport] [-w < watchPaths || false >] [-b]

**port** (default _8080_): Port to listen on

**dir** (default _._): Folder to serve

**url** (default _empty_): Path to open the specific page. _e.g._ `/#/main`

**livereloadport** (default _35729_): Port for the livereload server. If `false` the livereload is disabled.

**watchPaths**: Comma-separated list of glob patterns for the files to watch. _e.g._ `**/*.js,**/*.css,**/*.html,**/*.xml`

**b**: disable browser open

## Examples

Default usage

    > lr-http-server

    HTTP server listening on port 8080
    Serving <path>
    Livereload listening on port 35729
    Watching files:
      '<path>/**/*.html'
      '<path>/**/*.js'
      '<path>/**/*.css'
      '<path>/**/*.xml'

All options

    > lr-http-server -p 80 -d src/ -u /#/main -l 30000 -w **/*.css,*.html

    HTTP server listening on port 80
    Serving <path>/src
    Open page in browser <path>/src/#/main
    Livereload listening on port 30000
    Watching files:
      <path>/src/**/*.css
      <path>/src/*.html
npm package: @olegkapustin/test_npmcicd
Description: npm CI/CD test
Author: Oleg Kapustin
Latest version: 0.1.2

# Test - NPM CI/CD

This package is for exploring NPM CI/CD via github actions. The package doesn't
implement anything useful - just a 'hello world!' kind of thing.

## ToDo

- [x] build/test pipeline
- [ ] ~~package publishing - develop/dev~~ - we can't publish same version twice
      re-tagging after merge to `main` doesn't sound like a good idea.
- [x] package publishing - main/latest
- [x] version bump CI/CD step

## License

[MIT](./LICENSE)
npm package: @olegrumiancev/sp-react-formfields
Description: Collection of React controls used for rendering SharePoint fields in custom forms. Support new/edit/display rendering modes.
Author: Oleg Rumiancev
Latest version: 0.7.2

# @olegrumiancev/sp-react-formfields [![NPM version](https://badge.fury.io/js/%40olegrumiancev%2Fsp-react-formfields.svg)](https://npmjs.org/package/@olegrumiancev/sp-react-formfields) [![Build Status](https://travis-ci.org/olegrumiancev/sp-react-formfields.svg?branch=master)](https://travis-ci.org/olegrumiancev/sp-react-formfields)

> Collection of React controls used for rendering SharePoint fields in custom forms. Support new/edit/display rendering modes.

## Installation

```sh
$ npm install --save @olegrumiancev/sp-react-formfields
```

## Usage

```js
var olegrumiancevSpReactFormfields = require('@olegrumiancev/sp-react-formfields');
olegrumiancevSpReactFormfields();
```

## License

MIT © [Oleg Rumiancev](https://github.com/olegrumiancev)
npm package: @olegtsvetkov/n8n-nodes-calcarddav
Description: Use CalDAV and CardDAV APIs
Author: Oleg Tsvetkov
Latest version: 0.3.3

# n8n-nodes-calcarddav
⚠️ **WIP: Just started this based on the starter project to play around. It is not functional yet. Feel free to copy, continue, or provide PRs :)**

This is an n8n community node. It lets you use CalDAV and CardDAV APIs (like NextCloud) in your n8n workflows.

[CalDAV](https://datatracker.ietf.org/doc/html/rfc4791) is an open protocol to interact with calendars (creating events, reading events, updating events).
[CardDAV](https://datatracker.ietf.org/doc/rfc6352/) is an open protocol to interact with address books (creating contacts, reading address books, updating contacts)

## The Goal

1. Be able to interact with CardDAV APIs (such as NextCloud)
2. Be able to interact with CalDAV APIs (such as NextCloud)

## About N8N

[n8n](https://n8n.io/) is a [fair-code licensed](https://docs.n8n.io/reference/license/) workflow automation platform.

[Installation](#installation)  
[Operations](#operations)  
[Credentials](#credentials)  <!-- delete if no auth needed -->  
[Compatibility](#compatibility)  
[Usage](#usage)  <!-- delete if not using this section -->  
[Resources](#resources)  
[Version history](#version-history)  <!-- delete if not using this section -->  

## Installation

Follow the [installation guide](https://docs.n8n.io/integrations/community-nodes/installation/) in the n8n community nodes documentation.

## Operations

_List the operations supported by your node._

## Credentials

_If users need to authenticate with the app/service, provide details here. You should include prerequisites (such as signing up with the service), available authentication methods, and how to set them up._

## Compatibility

_State the minimum n8n version, as well as which versions you test against. You can also include any known version incompatibility issues._

## Usage

_This is an optional section. Use it to help users with any difficult or confusing aspects of the node._

_By the time users are looking for community nodes, they probably already know n8n basics. But if you expect new users, you can link to the [Try it out](https://docs.n8n.io/try-it-out/) documentation to help them get started._

## Resources

* [n8n community nodes documentation](https://docs.n8n.io/integrations/community-nodes/)
* _Link to app/service documentation._

## Version history

_This is another optional section. If your node has multiple versions, include a short description of available versions and what changed, as well as any compatibility impact._
npm package: @olegyanush/zephyr
Description: Zephyr Scale integration
Author: aleh.yanushkevich@enverus.com
Latest version: 1.0.8

## WDIO Enverus Zephyr Scale Integration
## About

## Getting Started
Once installed it can now be referenced by simply calling 
```javascript
import { ZephyrScaleReporter, ZephyrScaleService, TestCycle } from '@wdio-enverus/wdio-enverus-zephyrscale-reporter';
```


### How to use:

You have just to:
1. Define configuration for Zephyr Scale Reporter:
```javascript
const zephyrConfig = {
    url: 'https://api.zephyrscale.smartbear.com/v2/',
    projectKey: '<Jira project key>', // Project key in Jira
    accessToken: '<access token>', // Access token for calling Zephyr Scale API
    executedById: '<identifier of user>', // Identifier of an user what will be assigned to Cycle run as an executor.
    assignedToId: '<identifier of user>', // Identifier of an user what will be assigned to Cycle run.
    ignoreStepCondition: (title) => title.startsWith('[Ignore]'), // Condition for ignoring reporting steps. [OPTIONAL]
    cycleKey: '<Zephyr Scale cycle key>', // Cycle key, if you would like to report test execution to existed Test Cycle. [OPTIONAL]
    stepReporting: true, // Enable or disable steps reporting
    cycle: new TestCycle(
        `<Zephyr Scale cycle name>`,
        '<Zephyr Scale cycle description>')
};
```

2. Add ZephyrScaleReporter to WDIO reporters in config:
```javascript
config.reporters.push([ZephyrScaleReporter, zephyrConfig]);
```

3. Add ZephyrScaleService to WDIO services in config:
```javascript
config.services.push([ZephyrScaleService]);
```
npm package: @oleh-ob/eslint-standard-rules
Description: ESLint JavaScript standard configuration
Author: Oleh Obydonov
Latest version: 1.0.2

# The ESLint config of [JavaScript Standard Style](http://standardjs.com)

## Usage

```bash
npm install --save-dev eslint @oleh-ob/eslint-standard-rules
```


Example `eslint.config.mjs`:
```js
import standard from '@oleh-ob/eslint-standard-rules'

export default [
  standard
] 
```
npm package: @oleh-polishchuk/prettier-config
Description: My personal Prettier config
Author: Oleh Polishchuk
Latest version: 1.0.1

### `@oleh.polishchuk/prettier-config`

My personal [Prettier](https://prettier.io) config.

## Usage

**Install**:

```bash
$ yarn add --dev @oleh-polishchuk/prettier-config
```

**Edit `package.json`**:

```jsonc
{
  // ...
  "prettier": "@oleh-polishchuk/prettier-config"
}
```
npm package: @olehermanse/utils
Description: Utility functions in js / ts
Author: Ole Herman S. Elgesem
Latest version: 0.1.23

# Common js / ts utilities for personal use

I use these across a few different projects;

- https://github.com/olehermanse/trpg
- https://github.com/olehermanse/tpg
- https://github.com/olehermanse/towers

## Publishing new versions

Here are the steps to make a new version:

1. Check that `package.json` has the correct version:
   https://github.com/olehermanse/utils/blob/main/package.json#L3
   - It should be the version you want to release.
   - Change it if necessary, for example to bump major or minor version.
2. Create a release in GitHub:
   - Open https://github.com/olehermanse/utils/releases
   - **Draft a new release**
   - Put the version number in both tag (create a new tag) and name field
   - **Generate release notes**
3. Check that the release has been published on npm:
   - https://www.npmjs.com/package/@olehermanse/utils
   - This is done automatically by the GitHub Action after creating a release.
4. Check that the version number has been bumped in a PR:
   - https://github.com/olehermanse/utils/pulls
   - The GitHub Action will automatically make a PR bumping the version
   - Manually bump minor or major version if you know that is what you'll release next:
     - https://github.com/olehermanse/utils/blob/main/package.json#L3

Trusted publishing must be configured on npmjs.com there are no GH secrets / npm tokens.
npm package: @olehogn_packages/fn-example
Description: Test component
Author: Oleh Ogn
Latest version: 1.0.0

# @fn/fn-example

> Test component

[![NPM](https://img.shields.io/npm/v/@fn/fn-example.svg)](https://www.npmjs.com/package/@fn/fn-example) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)

## Install

```bash
npm install --save @fn/fn-example
```

## Usage

```tsx
import React, { Component } from 'react'

import MyComponent from '@fn/fn-example'
import '@fn/fn-example/dist/index.css'

class Example extends Component {
  render() {
    return <MyComponent />
  }
}
```

## License

MIT © [](https://github.com/)