open-index/open-npm huggingface dataset:
npm package: @maddeveloper/node-websockify
Description: node-websockify is a WebSocket-to-TCP proxy/bridge you can use in a NodeJS program
Author: Julien Sergent | MadDeveloper
Latest version: 1.0.10

# WebSocket-to-TCP proxy/bridge in NodeJS (forked & inspired by https://github.com/novnc/websockify)

[![License](https://img.shields.io/badge/license-MIT-green.svg?style=flat)](https://github.com/maddeveloper/node-websockify/blob/master/LICENSE.md)

Node-websockify is a WebSocket-to-TCP proxy/bridge you can use in a NodeJS program.

As said it is inspired of the javascript library of https://github.com/novnc/websockify. Unfortunately this library can't be used directly in a nodeJS program. Thats the reason why I created this project.

## Usage

Import this module in your project

```bash
npm install --save @maddeveloper/node-websockify
```

Require the module and call the main function in your program code

```javascript
import websockify from "@maddeveloper/node-websockify"

const [webServer, wsServer, error] = websockify({
  source: "url:port",
  target: "url:port",
  web: "./directory",
  cert: "certSSL",
  key: "certSSL-key",
})
```

Example :

```javascript
import websockify from "@maddeveloper/node-websockify"

const [webServer, wsServer, error] = websockify({
  source: "127.0.0.1:8080",
  target: "192.168.0.100:5900",
})
```

## Params

| Name            | Description                                       | Default         |
| --------------- | ------------------------------------------------- | --------------- |
| source          | URL of websocket Server                           | null            |
| target          | URL of the VNC Server                             | null            |
| web             | Directory of static sources exposed by the server | null (optional) |
| cert            | Path of the SSL certificate                       | null (optional) |
| key             | Key of the SSL certificate                        | null (optional) |
| server          | HTTP server to use                                | null (optional) |
| webSocketServer | WebSocket server to use                           | null (optional) |

## Options

| Name           | Description                                       | Default   |
| -------------- | ------------------------------------------------- | --------- |
| onConnected    | Called when connection is established with target | undefined |
| onDisconnected | Called when connection is interruped with target  | undefined |

## CLI usage

```bash
websockify [--web web_dir] [--cert cert.pem [--key key.pem]] [source_addr:]source_port target_addr:target_port
```
npm package: @maddiek/sve-ui
Description: Social Value Engine shared UI components — footer, brand tokens, and Tailwind preset
Author: maddiek
Latest version: 1.2.0

# @maddiek/sve-ui

Shared UI components for Social Value Engine websites.

## Install

```bash
npm install @maddiek/sve-ui
```

## SveFooter

A "Part of the SVE family" sister sites strip — drop it into any SVE family site to show the network of related platforms.

```tsx
import { SveFooter } from "@maddiek/sve-ui";

export default function App() {
  return (
    <>
      {/* your page content and footer */}
      <SveFooter />
    </>
  );
}
```

Renders a dark `#01343F` band with the label "Part of the SVE family" and links to all five sister sites. No logo needed — just drop it in.

### Props

| Prop | Type | Default | Description |
|------|------|---------|-------------|
| `sites` | `SveSisterSite[]` | All five SVE sites | Override the list of sites shown |

### SveSisterSite

```ts
interface SveSisterSite {
  name: string;
  href: string;
}
```

### Default sites

- Rose Regeneration — roseregeneration.co.uk
- Impact Card Studio — impactcardstudio.com
- Place Explorer — place.socialvalueengine.com
- My Impact — app.myimpact.social
- Social Value Direct — direct.socialvalueengine.com

## Tailwind Preset

Adds SVE brand colour tokens to any Tailwind project.

```js
// tailwind.config.js
import svePreset from "@maddiek/sve-ui/tailwind-preset";

export default {
  presets: [svePreset],
  content: [
    "./src/**/*.{ts,tsx}",
    "./node_modules/@maddiek/sve-ui/dist/**/*.js",
  ],
};
```

Available colour tokens: `sve-primary`, `sve-teal`, `sve-olive`, `sve-gold`, `sve-bg`, `sve-gray`.
npm package: @maddin.no/adr-viewer
Description: ADR Markdown Viewer Web Application Creator
Author: Martin Goldhahn
Latest version: 0.1.3


# ADR Viewer

A web-based viewer for Architecture Decision Records (ADRs) with filtering and navigation capabilities.

## Quick Start

```bash
npx @maddin.no/adr-viewer
```

This will build and serve the ADR viewer on `http://localhost:4173`.

## Installation

### Global Installation
```bash
npm install -g @maddin.no/adr-viewer
adr-viewer
```

### Local Project Usage
```bash
npm install @maddin.no/adr-viewer
npx adr-viewer
```

## Usage

1. Place your ADR markdown files in an `adrs-example/` directory in your project root
2. Run `npx @maddin.no/adr-viewer` or `adr-viewer` if installed globally
3. Open your browser to `http://localhost:4173`
4. Browse and filter your ADRs using the sidebar

## ADR Format

Your ADR files should follow this format:

```markdown
---
title: Your ADR Title
status: Draft|Accepted|Rejected|Deprecated
date: YYYY-MM-DD
author: Author Name
tags: []
---

# KEY-ID: Your ADR Title

## Status
Draft

## Context
Describe the context and problem statement.

## Decision
Describe the decision that was made.

## Consequences

### Positive
- List positive consequences

### Negative
- List negative consequences

## Alternatives Considered
1. **Alternative 1** - Description and why rejected

## Implementation Notes
- Implementation details
```

## Features

- 📁 Automatic ADR discovery and parsing
- 🔍 Filter by status and project keys
- 📱 Responsive design
- 🎨 Clean, modern interface
- 🚀 Fast navigation between ADRs

## Development

```bash
# Clone the repository
git clone <your-repo-url>
cd adr-viewer

# Install dependencies
npm install

# Start development server
npm run dev

# Build for production
npm run build

# Preview production build
npm run preview
```

## Publishing to NPM

To publish this package to NPM under the `@maddin.no` organization, you'll need to:

1. **Prerequisites:**
   - Have an NPM account and be a member of the `maddin.no` organization
   - Be logged in to NPM: `npm login`

2. **Manual package.json updates needed:**
   Add these fields to your `package.json`:
   ```json
   {
     "name": "@maddin.no/adr-viewer",
     "version": "1.0.0",
     "description": "A web-based viewer for Architecture Decision Records (ADRs)",
     "bin": {
       "adr-viewer": "./bin/adr-viewer.js"
     },
     "files": [
       "dist/",
       "bin/",
       "README.md"
     ],
     "keywords": ["adr", "architecture", "decision", "records", "viewer", "documentation"],
     "author": "Your Name",
     "license": "MIT",
     "repository": {
       "type": "git",
       "url": "https://github.com/yourusername/adr-viewer.git"
     },
     "scripts": {
       "prepublishOnly": "npm run build"
     }
   }
   ```

3. **Verify organization access:**
   ```bash
   npm org ls maddin.no
   ```

4. **Build the project:**
   ```bash
   npm run build
   ```

5. **Publish:**
   ```bash
   npm publish --access public
   ```

## License

MIT