open-index/open-npm huggingface dataset:
npm package: @floomhq/cli
Description: Deploy Python functions as live web apps
Latest version: 0.1.8

# @floomhq/cli

Deploy Python functions as live web apps from the terminal.

## Install

```bash
npm install -g @floomhq/cli
```

## Setup

```bash
export FLOOM_URL=http://localhost:3001   # your floom server
export FLOOM_API_KEY=your-api-key        # optional for OSS mode
```

## Usage

### Deploy

```bash
# Deploy a Python file
floom deploy my_script.py

# Deploy with a name
floom deploy my_script.py --name "Flight Finder"

# Deploy a ZIP with requirements.txt
floom deploy project.zip
```

### Run

After deploying, run your app from the browser or use the client SDK.

### Manage

```bash
floom list                        # List all apps
floom logs my-app                 # View recent run logs
floom open my-app                 # Open in browser
floom delete my-app               # Delete an app

# Versions
floom versions my-app             # List versions
floom promote my-app              # Promote dev to production
floom rollback <version_id>       # Rollback to a version

# API Keys (secrets)
floom secrets list my-app
floom secrets set my-app API_KEY sk-123
floom secrets delete my-app API_KEY

# Persistent storage
floom storage list my-app
floom storage get my-app counter
floom storage set my-app counter 42

# Share links
floom share create my-app
floom share list my-app

# Health check
floom doctor
```

### Project Context

After deploying, the CLI saves project context to `.floom/project.json`. Subsequent commands auto-detect the app ID, so you can run `floom logs` without specifying an app name.

## License

MIT
npm package: @floomhq/client
Description: JavaScript client for Floom
Latest version: 0.1.8

# @floomhq/client

JavaScript/TypeScript client for the Floom API.

## Install

```bash
npm install @floomhq/client
```

## Usage

```typescript
import { FloomClient } from '@floomhq/client';

const client = new FloomClient({
  url: 'http://localhost:3001',
  apiKey: 'your-api-key',  // optional for OSS mode
});

// Deploy Python code
const project = await client.deploy(
  'def run(city: str = "Berlin") -> dict:\n  return {"message": f"Hello {city}"}',
  'Greeter'
);

// Run an endpoint
const run = await client.run(
  project.id,
  project.version_id,
  project.endpoints[0].id,
  { json: { city: 'Hamburg' } }
);

// Wait for result
const result = await client.waitForRun(run.run_id);
console.log(result.result?.json);
// { message: "Hello Hamburg" }
```

## API

### Core

- `deploy(code, name, requirements?, config?)` - Deploy Python code or base64 ZIP
- `run(projectId, versionId, endpointId, params?)` - Execute an endpoint
- `waitForRun(runId, timeoutMs?)` - Poll until completion (default 120s)
- `getRunStatus(runId)` - Get run status and result
- `listProjects()` - List all projects
- `getProject(projectId)` - Get project details with endpoint schemas
- `deleteProject(projectId)` - Delete a project

### Versions

- `listVersions(projectId)` - List versions with dev/prod flags
- `promote(projectId, versionId?)` - Promote to production
- `rollback(projectId, versionId)` - Rollback

### Secrets

- `listSecrets(projectId)` - List configured secrets
- `setSecret(projectId, key, value)` - Set a secret
- `deleteSecret(projectId, key)` - Delete a secret

### Storage

- `putStorage(projectId, key, value)` - Store a value
- `getStorage(projectId, key)` - Retrieve a value
- `deleteStorage(projectId, key)` - Delete a value
- `listStorage(projectId)` - List all keys

### Share Links

- `createShareLink(projectId)` - Create public share link
- `listShareLinks(projectId)` - List share links
- `disableShareLink(projectId, shareId)` - Disable a link

## License

MIT
npm package: @floongyex/eslint-config-styling
Description: ESLint share configurations that focus on code style checking and formatting.
Author: FloongyEX
Latest version: 0.2.0

# eslint-config-styling

<div align="center">
  <span>🌐 Language</span><br>
  <a href="README.md">English</a>
  <span>|</span>
  <span>简体中文</span>
</div>

ESLint 可共享配置，基于 [ESLint Stylistic](https://eslint.style/)
定制，包含了与代码格式/风格相关的 ESLint 规则，专注于代码风格检查与格式化。

此配置是基于我个人的需求配置的，不一定适合您的需求，建议查看[规则](#规则)以确认是否符合您的风格需求。

## 安装

将此包作为开发依赖（devDependency）安装：

```shell
npm install --save-dev  @floongyex/eslint-config-styling  
```

## 使用方法

将共享配置对象添加到您的 ESLint 扁平化配置文件的配置数组中：

```JavaScript file:eslint.config.js
import { defineConfig } from "eslint/config"
// 导入配置
import stylingConfig from '@floongyex/eslint-config-styling'

export default defineConfig([
  // 你的其他配置项
  // ……

  // 添加配置
  stylingConfig.stylistic,
])
```

更多信息请参阅 [ESLint 官方文档](https://eslint.org/docs/head/use/configure/configuration-files)。

## 规则

可以查看源代码（[stylistic](lib/stylistic.js)）来了解已配置的规则。

关于规则的更多信息请参阅 [ESLint Stylistic 规则](https://eslint.style/packages/default#rules)。

## 许可证

MIT © FloongyEX
npm package: @floorplan/base
Description: The place to start for making a component library.
Author: Brian Bartholomew
Latest version: 0.0.1

# floorplan-base
The place to start for making a component library.


### Hi!

This repo is a starting place for a component library. Simply clone this and add what you want.

### Dependancies

The dependancies are add completely based on opinion. There are other ways to accomplish this but, these are some of the more popular tools in the industry. The main goal here is that if you run into problems you hopefully wont be the first one and can google for an answer.

### What's in here?

In here you will see the dev build tools and dev tools. You will not see frame works like React, Angular, Vue, etc. You also wont see css frame work decisions here. This allows every one to start here and make choices like that based on their opinions. It is recommended to use storybook for the testing environment but it is not necessary, and therefore not included at this stage.

### Philosophy

Everything in here is based on atomic design. The component library will only consist of atoms, molecules and organisms. Anything beyond that in atomic design is contextual and does really belong here. These these begin to be to related to implementation and not really sharable. Think about it this way, if you were to open source your library would it make sense for you to share all the pieces in there. The moment you identify pieces that don't make sense you should find a place for them else where.
npm package: @floorplanner/quadtree
Description: A simple quadtree implementation
Author: Tim Knip
Latest version: 1.0.4

## quadtree

A simple quadtree implementation.

![alt quadtree](https://content.screencast.com/users/TimKnip/folders/Jing/media/2e40667f-baf3-416c-98ff-ef8ef372271b/2018-03-26_1312.png)

### live demo

[live demo](https://rawgit.com/floorplanner/quadtree/master/html/index.html)

### install

    npm i @floorplanner/quadtree

### api

#### exports

-  `QuadTree` The QuadTree
-  `QuadTreeBoundary` A bounding box to be used with `QuadTree::retreive`

#### static methods

-  `QuadTree.create(x, y, width, height, capacity, max_level)` Creates the quadtree.

#### instance methods

##### QuadTree

-  `insert(x, y, data = null)` Inserts an item at the specified coordinates.
-  `traverse(cb = null)` Traverses the tree, takes an optional callback method.
-  `query(bounds)` Retreives all data inside the specified bounds

##### QuadTreeBoundary

-  `new QuadTreeBoundary(x0, y0, x1, y1)` - Constructor

### example

```javascript

import {Quadtree, QuadTreeBoundary} from '@floorplanner/quadtree';

let width = 800;    // width of the tree
let height = 600;   // height of the tree
let capacity = 10;  // capacity of a node
let max_level = 5;  // maximum recursion depth

let tree = QuadTree.create(0, 0, width, height, capacity, max_level);

tree.insert(100, 100, {text: 'some data'});

tree.traverse(function (node) {
    console.log(node.level, node.data);
});

let data = tree.query(new new QuadTreeBoundary(0, 0, 200, 200));

console.log(data);

```