open-index/open-npm huggingface dataset:
npm package: @posten/hedwig-react
Description: Hedwig react components
Author: Posten
Latest version: 0.6.17
Deprecated: Package no longer supported. Use @postenbring/hedwig-react instead

# hedwig-react

> Hedwig react components

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

## Install

```bash
npm install @posten/hedwig-react
```

## Icons
We are using icons from Font Awesome Pro wich requires you to obtain a licence. The auth token from your licence will need to be added to an environment variable. For Posten and Bring developers, please contact the Hedwig contributors for this token. For other users, a licence can be obtained <a href="https://fontawesome.com">here</a>

```bash
export NPM_TOKEN=[your auth token]
```

## Styling
Our components are functional components only, so you will still have to import fonts and styling 
```bash
<link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/@posten/hedwig@{version}/assets/fonts.css">
<link rel="stylesheet" type="text/css" href="https://cdn.jsdelivr.net/npm/@posten/hedwig@{version}/dist/{posten/bring}.css">
```

## Usage

```jsx
import { Badge } from '@posten/hedwig-react'

<Badge>Hello world</Badge>
```

## License

MIT © [Bring](https://github.com/Bring)
npm package: @postenbring/hedwig-tokens
Description: Design tokens for [Hedwig Design System](https://github.com/bring/hedwig-design-system).
Latest version: 2.0.1

# @postenbring/hedwig-tokens [![npm version](https://badge.fury.io/js/@postenbring%2Fhedwig-tokens.svg)](https://badge.fury.io/js/@postenbring%2Fhedwig-tokens)

Design tokens for [Hedwig Design System](https://github.com/bring/hedwig-design-system).
npm package: @posterboy/aws-region-latency-checker
Description: Library for checking AWS regions latency.
Author: carlos@technogi.com.mx
Latest version: 0.2.1

# Welcome to @posterboy/aws-region-latency-checker 👋
![Version](https://img.shields.io/badge/version-0.1.1-blue.svg?cacheSeconds=2592000)
[![Documentation](https://img.shields.io/badge/documentation-yes-brightgreen.svg)](https://github.com/Technogi/aws-region-latency-checker#readme)
[![Maintenance](https://img.shields.io/badge/Maintained%3F-yes-green.svg)](https://github.com/Technogi/aws-region-latency-checker/graphs/commit-activity)
[![License: MIT](https://img.shields.io/github/license/Technogi/@posterboy/aws-region-latency-checker)](https://github.com/Technogi/aws-region-latency-checker/blob/main/LICENSE)

> Library for checking AWS regions latency. Based on super cool post https://blog.risingstack.com/measuring-http-timings-node-js/

### 🏠 [Homepage](https://github.com/Technogi/aws-region-latency-checker#readme)

## Install

```sh
npm install @posterboy/aws-region-latency-checker 
```

## Usage

Just import the library select the region and select the mode for latency resolution:

### Modes:
- 'dns lookup'
- 'tcp connection'
- 'tls handshake'
- 'first byte'
- 'content transfer' (*default)

### Implementations
- axios (*default)
- https

### Example

```typescript
import {checkLatencies,checkLatency} from '@posterboy/aws-region-latency-checker'

// use all available regions and default mode 'first byte'
const results = await checkLatencies()

// specify regions and mode
const results = await checkLatencies(['us-west-2','us-east-1'],'dns-lookup','https')

// check latency for a single region
const results = await checkLatency('us-east-1','dns-lookup')

```


## Author

👤 **Carlos H**

* Website: http://www.technogi.com.mx
* Github: [@Technogi](https://github.com/Technogi)
* Email: carlos@technogi.com.mx

## 🤝 Contributing

Contributions, issues and feature requests are welcome!

Feel free to check [issues page](https://github.com/Technogi/aws-region-latency-checker/issues). You can also take a look at the [contributing guide](https://github.com/Technogi/aws-region-latency-checker/blob/main/CONTRIBUTING.md).

## Show your support

Give a ⭐️ if this project helped you!


## 📝 License

Copyright © 2021 [carlos@technogi.com.mx](https://github.com/Technogi).

This project is [MIT](https://github.com/Technogi/aws-region-latency-checker/blob/main/LICENSE) licensed.

***
_This README was generated with ❤️ by [readme-md-generator](https://github.com/kefranabg/readme-md-generator)_
npm package: @posterno/google-maps-html-marker
Description: A tiny javascript helper library to create html markers with Google maps.
Author: Alessandro Tesoro
Latest version: 1.0.0

# Google Maps HTML Markers

A tiny javascript helper library to create html markers with Google maps.

## Installation

```shell
npm install @posterno/google-maps-html-marker
```

or 

```shell
yarn add @posterno/google-maps-html-marker
```

## Usage

Load the helper library in your javascript file:

```js
const createHTMLMapMarker = require( 'google-maps-html-marker' );

const latLng = new google.maps.LatLng(16.7666, -3.0026);
const mapOptions = {
	zoom: 11,
	center: latLng
};
const map = new google.maps.Map(document.getElementById("map"), mapOptions);

let marker = createHTMLMapMarker({
	latlng: latLng,
	map: map,
	html: `<img id="parrot" src="https://cultofthepartyparrot.com/parrots/hd/parrot.gif">`
});

marker.addListener("click", () => {
	alert("Partyin Partyin Yeah!");
});
```

### Credits

This library was originally created by Dan Ward and published as [a tutorial here](https://levelup.gitconnected.com/how-to-create-custom-html-markers-on-google-maps-9ff21be90e4b). 

I've simply converted it to an ES5 javascript module and published it on the npmjs registry so that it's easier to re-use for my projects.
npm package: @posterno/posterno-release
Description: CLI Shell for preparing a release of the Posterno WordPress plugin.
Author: pressmodo
Latest version: 0.1.3

# Posterno release preparation shell


A command line tool to prepare the main core Posterno WordPress plugin folder for a public release on wp.org.

## Why

The main posterno repository does not contain the whole code of the plugin. The plugin contains components that are developed separately from the core and loaded through composer.

During development, a component is symlinked via composer through the component's local folder on your computer. However when the plugin needs to be publicly released, the release must contain the latest stable version of all components.

This command line tool, automatically removes locally symlinked components and installs the latest stable version of each component registered in Posterno. A final .zip file can then be prepare through Grunt.

## Installation

Run the command:

```
npm install @posterno/posterno-release -g
```

## How it works

The following are the steps that this utility performs on your system.

- Verifies that a posterno-components.json file is available. This is where all components are registered.
- Queries Github api to check the latest released tags for each registered package.
- Removes symlinked development Posterno composer packages.
- Installs the stable version of each package.
- Runs the Grunt.js `build` task defined into the main Posterno plugin.
- Removes stable Posterno composer packages.
- Re-installs the local symlinked packages.

## Usage

- Navigate to the main Posterno core plugin folder via your terminal.
- Run the command `posterno-prepare-release`.
- Sit back and watch a release automagically complete.
npm package: @posterno/vue-form-components
Description: Collection of Vue.js form components used on the frontend for forms powered by Posterno.
Author: Alessandro Tesoro
Latest version: 0.1.2

# Posterno Vue.js Form components

![Plugin Version](https://img.shields.io/wordpress/plugin/v/posterno.svg?color=%235c6ac5&label=Latest%20release) ![Downloads](https://img.shields.io/wordpress/plugin/dt/posterno.svg?color=%2346b450&label=Downloads&style=popout) ![Rating](https://img.shields.io/wordpress/plugin/rating/posterno.svg?color=%2346b450&label=Rating) ![tested](https://img.shields.io/wordpress/plugin/tested/posterno.svg?color=%2346b450&label=WordPress)

Collection of Vue.js form components used on the frontend for forms powered by Posterno.

## Credits

Big thanks to https://github.com/heyui/heyui - the components available in this repository, have been taken from HeyUI and slightly modified to be compatible with Posterno.

## Development installation

Run command:

```js
yarn add @posterno/vue-form-components
```

## Development setup

##### Install dependencies
```
yarn install
```

##### Use storybook.js for preview
```
yarn storybook
```

##### Compiles and hot-reloads for development
```
yarn run serve
```

##### Compiles and minifies for production
```
yarn run build
```

##### Lints and fixes files
```
yarn run lint
```

##### Run your unit tests
```
yarn run test:unit
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).

## Documentation

* [Posterno Documentation](https://docs.posterno.com)

## Support

This repository is not suitable for support. Please don't use the issue tracker for support requests. Support can take place through the appropriate channels:

* The [Posterno premium support portal](https://posterno.com/support/) for customers who have purchased themes or extensions.
* [Our community forum on wp.org](https://wordpress.org/support/plugin/posterno) which is available for all Posterno users.

Support requests in issues on this repository will be closed right away.
npm package: @posteverywhere/mcp
Description: PostEverywhere MCP Server — manage social media from Claude Code
Author: PostEverywhere
Latest version: 1.1.0

# PostEverywhere MCP Server

Manage your social media directly from [Claude Code](https://claude.com/claude-code) — schedule posts, manage accounts, generate AI images, and publish across all platforms.

## Setup

### 1. Get your API key

```bash
npx posteverywhere init
```

### 2. Add to Claude Code

Add to your `claude_desktop_config.json` or `.claude/mcp.json`:

```json
{
  "mcpServers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": {
        "POSTEVERYWHERE_API_KEY": "pe_live_your_key_here"
      }
    }
  }
}
```

### 3. Use it

Just ask Claude:

- *"Show me my connected social accounts"*
- *"Post 'Hello world!' to all my accounts"*
- *"Schedule a post for tomorrow at 9am EST"*
- *"Generate an AI image of a sunset and post it to Instagram"*
- *"Show me my recent posts"*
- *"Retry the failed post"*

## Available Tools

| Tool | Description |
|------|-------------|
| `list_accounts` | List all connected social media accounts |
| `get_account` | Get details for a specific account |
| `list_posts` | List scheduled and published posts |
| `create_post` | Create and publish or schedule a post |
| `get_post` | Get post details with per-platform status |
| `get_post_results` | Get publish results per platform |
| `delete_post` | Delete a post |
| `retry_post` | Retry failed post destinations |
| `list_media` | List uploaded media files |
| `get_media` | Get media file status |
| `delete_media` | Delete a media file |
| `generate_image` | Generate an AI image from a text prompt |

## Supported Platforms

Instagram, TikTok, YouTube, LinkedIn, Facebook, X (Twitter), and Threads.

## Links

- [PostEverywhere](https://posteverywhere.ai) — Social media management platform
- [API Documentation](https://developers.posteverywhere.ai) — Full API reference
- [Dashboard](https://app.posteverywhere.ai) — Manage your accounts
- [npm SDK](https://www.npmjs.com/package/posteverywhere) — Node.js/TypeScript SDK
- [Pricing](https://posteverywhere.ai/pricing) — Plans from $19/mo with 14-day free trial
npm package: @postgres-language-server/backend-jsonrpc
Description: Bindings to the JSON-RPC Workspace API of the Postgres Language Tools daemon
Author: Supabase Community
Latest version: 0.24.0

<div align="center">
  <img src="docs/images/pls-github.png" alt="Postgres Language Server" width="80%">

____

  A collection of language tools and a Language Server Protocol (LSP) implementation for Postgres, focusing on developer experience and reliable SQL tooling.

  [Documentation](https://pg-language-server.com/latest/) | [Installation](https://pg-language-server.com/latest/getting_started/) | [CLI Releases](https://github.com/supabase-community/postgres-language-server/releases)

  [VSCode](https://marketplace.visualstudio.com/items?itemName=Supabase.postgrestools) | [Cursor](https://open-vsx.org/extension/supabase/postgrestools) | [Neovim](https://github.com/neovim/nvim-lspconfig/blob/master/doc/configs.md#postgres_lsp) | [Zed](https://github.com/LoamStudios/zed-postgres-language-server) | [Sublime Text](https://lsp.sublimetext.io/language_servers/#postgresql)
</div>

## Overview

LSP Demo             |  CLI Demo
:-------------------------:|:-------------------------:
![LSP Demo](/docs/images/lsp-demo.gif)  |  ![CLI Demo](/docs/images/cli-demo.png)

This project provides a toolchain for Postgres development, built on Postgres' own parser `libpg_query` to ensure 100% syntax compatibility. It is built on a Server-Client architecture with a transport-agnostic design. All features can be accessed through the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/), a CLI, HTTP APIs, and a WebAssembly module. The goal is to make all the great Postgres tooling out there as accessible as possible, and to build anything that is missing ourselves.

The following features are available today:

- [Autocompletion & Hover](https://pg-language-server.com/latest/features/editor_features/)
- [Syntax Diagnostics](https://pg-language-server.com/latest/features/syntax_diagnostics/)
- [Type Checking](https://pg-language-server.com/latest/features/type_checking/) (via `EXPLAIN` error insights)
- [Formatting](https://pg-language-server.com/latest/features/formatting/)
- [Migration Linting](https://pg-language-server.com/latest/features/linting/)
- [Database Linting](https://pg-language-server.com/latest/features/database_linting/)
- [PL/pgSQL Support](https://pg-language-server.com/latest/features/plpgsql/)

## Development

```bash
nix develop     # or skip if not using Nix
docker-compose up -d
```

## Acknowledgements

A big thanks to the following projects, without which this project wouldn't have been possible:

- [libpg_query](https://github.com/pganalyze/libpg_query): For extracting the Postgres' parser
- [Biome](https://github.com/biomejs/biome): For implementing a toolchain infrastructure we could copy from
- [Squawk](https://github.com/sbdchd/squawk): For the linter inspiration
npm package: @postgres-queries/builder
Description: Query builder for PostgreSQL in Node.js, built for async
Author: Marmelab
Latest version: 0.2.1

# Queries Builder

All query factories function takes an object as a parameter, containing the following keys:

- **table:** table name on which operate the query,
- **permanentFilters:** query filters provided to each underlying queries, as a plain object

## Count

Build a `COUNT(*)` query.

```js
import { countAll } from "postgres-queries-builder";

const countQuery = countAll({
  table: "user",
  permanentFilters: {
    active: 1
  }
});

countQuery({
  filter: {
    department: "HR"
  }
});

// SELECT COUNT(*) FROM user WHERE active = 1 AND departement = "HR"
```

The `countQuery` takes an extra object parameter whose keys are:

- **filter:** extra filter to apply to the query, as a plain object