open-index/open-npm huggingface dataset:
npm package: @fastintegration/icons
Description: Fastintegrations Iconset
Author: lf.amorim@bipbop.com.br
Latest version: 1.0.7
Deprecated: false

# @fastintegration&#x2F;icons@1.0.6
Fastintegrations Iconset

## Installation
Download node at [nodejs.org](http://nodejs.org) and install it, if you haven't already.

```sh
npm install @fastintegration/icons --save --registry https://npm.bipbop.com.br/
```

This package is provided in these module formats:

- CommonJS

## Dependencies

- [preact](https://github.com/developit/preact): Fast 3kb React alternative with the same ES6 API. Components & Virtual DOM.


## Dev Dependencies

- [eslint-config-airbnb](https://github.com/airbnb/javascript): Airbnb's ESLint config, following our styleguide
- [eslint-plugin-import](https://github.com/benmosher/eslint-plugin-import): Import with sanity.
- [eslint-plugin-jsx-a11y](https://github.com/evcohen/eslint-plugin-jsx-a11y): Static AST checker for accessibility rules on JSX elements.
- [eslint-plugin-react](https://github.com/yannickcr/eslint-plugin-react): React specific linting rules for ESLint
- [rollup-plugin-alias](https://github.com/frostney/rollup-plugin-alias): Resolves aliases with Rollup
- [rollup-plugin-istanbul](https://github.com/artberri/rollup-plugin-istanbul): Seamless integration between Rollup and Istanbul.
- [rollup-plugin-license](https://github.com/mjeanroy/rollup-plugin-license): Rollup plugin to add license banner to the final bundle and output third party licenses
- eslint
- gulp
- rollup
- rollup-plugin-buble
- rollup-plugin-commonjs
- rollup-plugin-node-resolve


## License
[MIT]()
npm package: @fastjsui/fastui
Description: Fast UI Packages
Author: fastjsui
Latest version: 0.0.3

<h1 align="center">🎉🚀Fast UI 组件库🎉 简介👋</h1>
<p>
  <img alt="Version" src="https://img.shields.io/badge/version-0.0.1-blue.svg?cacheSeconds=2592000" />
 <a href="https://opensource.org/licenses/ISC" target="_blank"> <img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-yellow.svg " /> </a> </br>
  <img src="https://img.shields.io/badge/node-%3E%3D16.14.2-blue.svg" />  
</p>


## 🏠 [项目主页](https://gitee.com/fastui)



> Fast UI 组件库

## ✨ [演示地址](https://www.fast-ui.com)

 
## 📦 环境要求


- node &gt;=16.14.2   
## 🛠️ 安装

```sh
pnpm install @fastjsui/fastui
```

 
## ✍️ 全局引用

```typescript
import { createApp } from 'vue'
import fastui from '@fastjsui/fastui'
import  '@fastjsui/fastui/style.css'
import App from './App.vue'

const app = createApp(App)

app.use(fastui).mount('#app')
```

 
## 🧪 按需引用

```sh
<script setup lang="ts">
// 单独使用
// import { FButton } from '@fastjsui/fastui/Button'
</script>

<template>
  // 按钮组件
  <f-button />
</template>
```

 
## 🧑 开发人员

- 🧑 fastjsui  
  - 🌏 Website: http://www.fast-ui.com 
  - 💼 GitHub: [@fastjsui](https://github.com/fastjsui)   
## 🤝 贡献

欢迎投稿、问题和功能请求！ [issues 地址](issuesUrl). 
## ⭐️ 支持

如果项目对你有帮助，请给我一个 start⭐️ 吧! 
- 💼 GitHub: [@fastjsui](https://github.com/fastjsui)  

## 📝 License

 Copyright © 2022 [fastjsui](https://github.com/fastjsui).  This project is [MIT](./LICENSE) licensed. 

---

_This README was generated with ❤️ by [fast-readme](https://www.npmjs.com/package/@fastjsui/fast-readme)_
npm package: @fastkit/eslint-config
Description: @fastkit/eslint-config
Author: dadajam4
Latest version: 0.15.0


# @fastkit/eslint-config

🌐 English | [日本語](https://github.com/dadajam4/fastkit/blob/main/packages/eslint-config/README-ja.md)

## Documentation
https://dadajam4.github.io/fastkit/eslint-config/
npm package: @fastkit/stylelint-config
Description: @fastkit/stylelint-config
Author: dadajam4
Latest version: 0.16.0


# @fastkit/stylelint-config

🌐 English | [日本語](https://github.com/dadajam4/fastkit/blob/main/packages/stylelint-config/README-ja.md)

## Documentation
https://dadajam4.github.io/fastkit/stylelint-config/
npm package: @fastkit/stylelint-config-vue
Description: @fastkit/stylelint-config-vue
Author: dadajam4
Latest version: 0.3.0


# @fastkit/stylelint-config

🌐 English | [日本語](https://github.com/dadajam4/fastkit/blob/main/packages/stylelint-config-vue/README-ja.md)

## Documentation
https://dadajam4.github.io/fastkit/stylelint-config/
npm package: @fastlane-events/sunmi-cloud-printer
Description: Expo module for Sunmi cloud printer control (BLE/LAN/USB) with barcode, QR code, and ESC/POS support
Latest version: 0.3.8

# @fastlane-events/sunmi-cloud-printer

Expo module for Sunmi cloud printer control (BLE/LAN/USB) with barcode, QR code, and ESC/POS support

# API documentation

- [Documentation for the latest stable release](https://docs.expo.dev/versions/latest/sdk/@fastlane-events/sunmi-cloud-printer/)
- [Documentation for the main branch](https://docs.expo.dev/versions/unversioned/sdk/@fastlane-events/sunmi-cloud-printer/)

# Installation in managed Expo projects

For [managed](https://docs.expo.dev/archive/managed-vs-bare/) Expo projects, please follow the installation instructions in the [API documentation for the latest stable release](#api-documentation). If you follow the link and there is no documentation available then this library is not yet usable within managed projects &mdash; it is likely to be included in an upcoming Expo SDK release.

# Installation in bare React Native projects

For bare React Native projects, you must ensure that you have [installed and configured the `expo` package](https://docs.expo.dev/bare/installing-expo-modules/) before continuing.

### Add the package to your npm dependencies

```
npm install @fastlane-events/sunmi-cloud-printer
```

### Configure for Android




### Configure for iOS

Run `npx pod-install` after installing the npm package.

# Contributing

Contributions are very welcome! Please refer to guidelines described in the [contributing guide]( https://github.com/expo/expo#contributing).
npm package: @fastlane-labs/atlas-sdk
Description: An SDK for building dApps on top of Atlas
Author: FastLane Labs
Latest version: 2.2.0

# Atlas Javascript/Typescript SDK

## Quickstart

Install the SDK package with npm:

```bash
npm install @fastlane-labs/atlas-sdk
```

Install the SDK package with yarn:

```bash
yarn add @fastlane-labs/atlas-sdk
```

Import the package and initialize the SDK.

```js
import { AtlasSdk, FastlaneBackend } from "@fastlane-labs/atlas-sdk";
import { JsonRpcProvider } from "ethers";

// The following values must be adjusted
const chainId = 11155111;
const rpcUrl = "https://rpc.sepolia.org";
const atlasAuctioneerUrl = "https://auctioneer-fra.fastlane-labs.xyz";

// Create the SDK instance
const sdk = await AtlasSdk.create(
  new JsonRpcProvider(rpcUrl, chainId),
  chainId,
  new FastlaneBackend({endpoint: atlasAuctioneerUrl})
);
```

## References

The full API reference is described in this document: https://atlas-docs.pages.dev/atlas/sdks/typescript/methods.
npm package: @fastlane-labs/shbundler-sdk
Description: SDK for interacting with Fastlane's 4337 ShBundler
Author: Fastlane Labs
Latest version: 1.0.22

# shbundler-sdk

A TypeScript SDK for interacting with Fastlane's 4337 bundler (ShBundler), designed to simplify the submission of UserOperations with built-in support for Fastlane paymasters and Safe-based smart accounts.

## Installation

```bash
pnpm add @fastlane-labs/shbundler-sdk
```

## Example 

```typescript
import { createShBundlerClient } from "@fastlane-labs/shbundler-sdk";
import { privateKeyToAccount } from "viem/accounts";

const signer = privateKeyToAccount("0xYOUR_PRIVATE_KEY");

const client = await createShBundlerClient({
  signer,
  rpcUrl: "https://rpc.monadlabs.dev", 
  chain: monadTestnet, // a viem chain object
});

await client.sendUserOperation({
  target: "0xTargetAddress",
  data: "0xCallData",
});
```
npm package: @fastlanejs/api
Description: Tool to generate shape of fastlane actions and plugins API
Author: Ray Deck
Latest version: 1.1.4

# fastlane-codegen

API generator/extractor for Fastlane

Generates the shape of fastlane actions and their options based on the currently installed version.

This is useful for generating a wrapper API over the `socket_server` interface.

## CLI

The easiest way to get started is running with `npx`

```bash
npx fastlane-api -f myapi.json
# or
npx fastlane-api > myapi.json
```

### Options

```bash
❯ npx fastlane-api --help
Usage: fastlane-api [options]

Generate JSON or YAML formatted API from Fastlane

Options:
  -f --file [filePath]  target file for serialized output (defaults to stdout)
  -d --debug            Debug mode - leave the fastlane directory and
                        auto-generated files behind (default: false)
  -y --yaml             Generate YAML instead of JSON (default: false)
  -h, --help            display help for command
```

## API

The export of `fastlane-api` is a function that generates the API as an object you can use in runtime.

### Installation

```bash
yarn add fastlane-api
```

### Usage

```js
const getFastlaneAPI = require("fastlane-api");
const { version, actions } = getFastlaneAPI(); //This is synchronous and slow
console.log("version is", api.version);
console.log(
  "Available actions are",
  actions.map(({ name }) => name)
);
```
npm package: @fastlanejs/base
Description: Base Interface for communicating with the fastlane socket server
Author: Ray Deck
Latest version: 2.0.12

# Fastlane-js

Javascript interface to Fastlane

## Requirements

**Fastlane** is required to have been installed: use `gem install Fastlane`

## Installation

```
yarn add @raydeck/fastlane
```

## Class Fastlane

### async doAction(action, arguments) => Promise<Any>

Returns the same result as running this Fastlane result in Ruby would. (note that there are excceptions where the Fastlane socket driver delivers suboptimal serializations of Ruby objects, such as with the action `adb_devices`). Starts the session automatically when you ask for the first action.

### async close() => Promise<Void>

Closes the connection to fastlane.

## async withFastlane(options: FastlaneOptions, func (fastlane: Fastlane)=> Promise)

The main helper function to control a Fastlane session.

- `options` (optional): Object of options to pass to the fastlane session:
  - `isInteractive: Boolean` whether to pass stdin/stdout of the socket server to the calling client. This should be `true` when you might need to respond to requests for, say, apple logins.
  - `port: Int` specify the port number of the connection (default `2000`)
- `func`: async function (returning a promise) containing the block of code to run during the Fastlane session, passed the `Fastlane` instance as its first and only argument. Note the session is initialized right before executing the function and closed right afterward.

## Example

```js
await withFastlane(async (fastlane) => {
  await fastlane.doAction("send_to_testflight", {
    application_id: "xxxx" /*...*/,
  });
});
// is the same as
await withFastlane({ isInteractive: true, port: 2000 }, async (fastlane) => {
  await fastlane.doAction("send_to_testflight", {
    application_id: "xxxx" /*...*/,
  });
});
// is the same as
await withFastlane(async ({ doAction }) => {
  await doAction("send_to_testflight", { application_id: "xxxx" /*...*/ });
});
// is the same as
const fastlane = new Fastlane(2000, true);
await fastlane.doAction("send_to_testflight", {
  application_id: "xxxx" /*...*/,
});
fastlane.close();
// is the same as
const fastlane = new Fastlane();
await fastlane.doAction("send_to_testflight", {
  application_id: "xxxx" /*...*/,
});
fastlane.close();
```

## Additional Helper functions

### async init(isInteractive = true) => Socket

Imperatively initialize the child Fastlane server process and connect using sockets. The socket is returned as a convenience, but don't mess with it unless you really know what you are doing.

- **isInteractive**: Boolean of whether to pass stdin/stdout of the socket server to the calling client. This should be `true` when you might need to respond to requests for, say, apple logins.

**Note**: This is run by default at the start of `withFastlane`

### async close() => Void

Close the connection to the Fastlane socket server and terminate the Fastlane socket server process.

**Note**: This is run by default at the end of `withFastlane`
npm package: @fastlooptech/layout-components
Description: A collection of layout components for React tailored on the needs of Fastloop
Author: Fastloop
Latest version: 0.1.5

# fastloop - Layout Components

This is a TypeScript library designed to simplify the process of managing layout and data in your React TypeScript projects. It consists of three components: Box, Space, and Stack.

## Features

- Lightweight and easy to use
- Zero dependencies
- Box component provides shortcuts for using the flex layout
- Space and Stack components provide additional layout options

## Installation

You can install this library via npm:

```bash
npm install @fastlooptech/layout-components
```

##Usage
To use this library, simply import the components you need into your TypeScript project:

```typescript
import { Box, Space, Stack } from '@fastlooptech/layout-components';
```

Then, you can use these components to manage your layout and data:

```typescript
<Box width={200} height={200} className="bg-teal">
  <Stack direction="column">
    <Box grow={1} className="bg-pink" />
    <Box grow={2} className="bg-orange" />
  </Stack>
</Box>
```

## License

This library is released under the MIT License.

## Contribution

We welcome contributions from anyone! If you'd like to contribute, please follow our contribution guidelines.

## Credits

This library was developed and is maintained by the FastLoop team.

## Feedback

If you have any feedback or suggestions for this library, please don't hesitate to open an issue. We appreciate your input!

## Support

If you need help with this library, please contact us at [info_at_fastloop.it](mailto:info@fastloop.it) or visit our website at [https://fastloop.it](https://fastloop.it/).
npm package: @fastly/compute-js-static-publish
Description: Static Publisher for Fastly Compute JavaScript
Author: Katsuyuki Omuro
Latest version: 7.0.6

# @fastly/compute-js-static-publish

Fastly Compute + KV Store for static websites and web apps.

This CLI tool helps you:

- ✅ Deploy static sites to Fastly Compute with zero backend
- 📦 Store files in Fastly KV Store efficiently
- 🗂 Publish to named collections (`live`, `preview-42`, etc.)
- 🔄 Switch between collections at runtime
- 🧹 Clean up old or expired assets

---

## Quick Start

Create a directory for your project, place your static files in `./public`, then type:

```sh
npx @fastly/compute-js-static-publish@latest --root-dir=./public --kv-store-name=site-content
```

### 🔧 Local Preview

```sh
cd compute-js
npm install
npm run dev:publish          # 'publish' your files to the simulated local KV Store
npm run dev:start            # preview locally
```

Serves your app at `http://127.0.0.1:7676`, powered by a simulated KV Store.

### 🚀 Deploy to Production

When you're ready to go live, [create a free Fastly account](https://www.fastly.com/signup/?tier=free) if you haven't already, and then:

```sh
cd compute-js
npm run fastly:deploy        # deploy the app
npm run fastly:publish       # upload your static files
```

In the future, unless you have further changes to make to your app itself, you can
upload further updates to your static files:
```sh
cd compute-js
npm run fastly:publish       # upload your static files
```

## Features

- Named collections for previews, staging, production
- SPA + fallback handling
- Precompressed Brotli/gzip support
- CLI tools for publish, promote, and cleanup

## Documentation

📘 Full documentation available on GitHub:  
[https://github.com/fastly/compute-js-static-publish](https://github.com/fastly/compute-js-static-publish)

### Security issues

Please see our [SECURITY.md](SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/ember-anti-clickjacking
Description: Anti-clickjacking support for ember
Author: Fastly
Latest version: 1.0.0

## Background

> Clickjacking, also known as a "UI redress attack", is when an attacker uses multiple transparent or opaque layers to trick a user into clicking on a button or link on another page when they were intending to click on the the top level page. Thus, the attacker is "hijacking" clicks meant for their page and routing them to another page, most likely owned by another application, domain, or both.

> Using a similar technique, keystrokes can also be hijacked. With a carefully crafted combination of stylesheets, iframes, and text boxes, a user can be led to believe they are typing in the password to their email or bank account, but are instead typing into an invisible frame controlled by the attacker.

- [OWASP Clickjacking](https://www.owasp.org/index.php/Clickjacking)

> One way to defend against clickjacking is to include a "frame-breaker" script in each page that should not be framed. The following methodology will prevent a webpage from being framed even in legacy browsers, that do not support the X-Frame-Options-Header.

- [OWASP Clickjacking Defense Cheat Sheet](https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet)

## What this library does

ember-anti-clickjacking adds some JavaScript that runs before the application
boots and prevents it from being rendered within the context of another page.

## Is this all I need?

No! Defense in depth is important for protecting against clickjacking because
of variations among browsers.

You should also be setting an appropriate `X-Frame-Options` header. If there are
no cases in which your application can be embedded, the safest thing to do is
deny framing altogether:

```http
X-Frame-Options: DENY
```

If you're using a
[Content Security Policy]([Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP))
(and you should be!), you should also set an appropriate `frame-ancestors` list.
To prevent embedding altogether, set it to `"none"`:

```http
Content-Security-Policy: frame-ancestors "none";
```

## Options

By default, ember-anti-clickjacking will inject

```html
<style id="antiClickjack">body{display:none !important;}</style>
```

into your `index.html`. This is a protection for some older browsers that allow
attackers to clobber `top.location`. Unfortunately, it doesn't play well with
`<noscript>`. If you're using a Content Security Policy, the `<style>` tag also
requires the `style-src 'unsafe-inline'` directive.

You can turn off the injection of the `<style>` tag as follows:

```js
// config/environment.js:

module.exports = function(environment) {
  var ENV = {
    'ember-anti-clickjacking': {
      style: false
    }
  }
  // ...
};
```
npm package: @fastly/expressly
Description: Express-style router for Fastly Compute.
Author: oss@fastly.com
Latest version: 2.4.0

# expressly
Express-style router for Fastly Compute.

## Using expressly

[Check out the docs](https://expressly.edgecompute.app/).

---

First, head over to [developer.fastly.com](https://developer.fastly.com) to get started with JavaScript on Fastly Compute:

1. Learn about Fastly Compute: [developer.fastly.com/learning/compute/](https://developer.fastly.com/learning/compute/)
2. Create your first JavaScript app: [developer.fastly.com/learning/compute/javascript/](https://developer.fastly.com/learning/compute/javascript/)

### Install expressly

Install expressly from the [npm registry](https://www.npmjs.com/package/@fastly/expressly):

```shell
npm i @fastly/expressly
```

```shell
yarn add @fastly/expressly
```

### Your first expressly app

Replace the contents of your Compute app's `src/index.js` with the following:

```javascript
import { Router } from "@fastly/expressly";

const router = new Router();

router.get("/", async (req, res) => {
  return res.send("Hello world!");
});

router.listen();
```

### Try it out

Start your app locally:

```shell
fastly compute serve
```

This will start your service on [http://localhost:7676](http://localhost:7676).

## Examples

Check out the JavaScript code examples for Compute on Fastly's [Developer Hub](https://developer.fastly.com/solutions/examples/javascript/).
npm package: @fastly/next-compute-js-server-12.3.0
Description: Next.js Runtime for Fastly Compute (12.3.0)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-12.3.3
Description: Next.js Runtime for Fastly Compute (12.3.3)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.0.1
Description: Next.js Runtime for Fastly Compute (13.0.1)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.0.3
Description: Next.js Runtime for Fastly Compute (13.0.3)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.0.7
Description: Next.js Runtime for Fastly Compute (13.0.7)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.1.3
Description: Next.js Runtime for Fastly Compute (13.1.3)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.1.6
Description: Next.js Runtime for Fastly Compute (13.1.6)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.2.0
Description: Next.js Runtime for Fastly Compute (13.2.0)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.2.4
Description: Next.js Runtime for Fastly Compute (13.2.4)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.3.0
Description: Next.js Runtime for Fastly Compute (13.3.0)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.3.2
Description: Next.js Runtime for Fastly Compute (13.3.2)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.4.1
Description: Next.js Runtime for Fastly Compute (13.4.1)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.4.3
Description: Next.js Runtime for Fastly Compute (13.4.3)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.4.4
Description: Next.js Runtime for Fastly Compute (13.4.4)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/next-compute-js-server-13.4.6
Description: Next.js Runtime for Fastly Compute (13.4.6)
Latest version: 0.3.1

# Next.js Runtime Server on Fastly Compute

This is an implementation of Next.js's BaseServer for
Fastly Compute, and the behavior is modeled highly off of NextNodeServer.
It enables running pages and API routes that target the `nodejs` runtime
on Compute.

NextWebServer (the Edge Runtime version) should be possible to run without
this port.

There is a separate library that corresponds to each release of Next.js,
maintained in separate branches of this library.

The versions of Next.js that this library is compatible with are listed in the
COMPATIBLE_NEXT_VERSIONS constant in `./src/node/function-transform/constants.ts`.

## Usage

This library is typically used with `@fastly/next-compute-js`, to implement the runtime
for pages and API routes that target the `nodejs` runtime. See `@fastly/next-compute-js` for
more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/next-compute-js-server/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/prettier-config
Description: Fastly's default eslint configuration
Author: Fastly
Latest version: 1.1.1

## @fastly/prettier-config

### Installation

```sh
npm install --save-dev @fastly/prettier-config
```

### Configuration

This will give you the recommended ruleset:

```js
// my-app/prettier.config.js
module.exports = require('@fastly/prettier-config')
```

You can override that as needed:

```js
// my-app/prettier.config.js
module.exports = Object.assign(
  {},
  require('@fastly/prettier-config'),
  {
    lineWidth: 120
  }
)
```
npm package: @fastly/remix-server-adapter
Description: Remix Adapter for Fastly Compute
Latest version: 4.2.0

# Remix Adapter for Fastly Compute

An adapter that allows the Compute JavaScript entry point program to start Remix.  This adapter
package we have created is designed to be used with Fastly Compute, and currently uses
[`@fastly/compute-js-static-publish`](https://github.com/fastly/compute-js-static-publish)
behind the scenes to include resources into the Wasm package bundle.

(`@fastly/compute-js-static-publish` is set up automatically for you if you set up your Remix
project using [`remix-template`](/packages/remix-template).)

## Usage

The simplest usage is the `createEventHandler` function.
This function needs to be passed the following parameters:

- `build`, obtained by loading `/build/index.js`
- `server`, obtained by calling `getServer()`, exported from `../static-publisher/statics.js`

> HINT: `../static-publisher/statics.js` is generated automatically by `@fastly/compute-js-static-publish`.

```js
/// <reference types="@fastly/js-compute" />  
import { createEventHandler } from '@fastly/remix-server-adapter';
import { moduleAssets, getServer } from '../static-publisher/statics.js';

/** @type {import('@remix-run/server-runtime').ServerBuild} */
const build = moduleAssets.getAsset('/build/index.js').getStaticModule();

/** @type {import('@fastly/compute-js-static-publish').PublisherServer} */
const server = getServer();

addEventListener("fetch", createEventHandler({ build, server }));
```

If you need more granular control over the `ServerBuild` module to use with Remix, or whether/how to handle static assets,
you may use the lower-level `createRequestHandler` and `handleAsset` functions:

```js
/// <reference types="@fastly/js-compute" />  
import { createRequestHandler, handleAsset } from '@fastly/remix-server-adapter';  
import { moduleAssets, getServer } from '../static-publisher/statics.js';

/** @type {import('@remix-run/server-runtime').ServerBuild} */
const build = moduleAssets.getAsset('/build/index.js').getStaticModule();

/** @type {import('@fastly/compute-js-static-publish').PublisherServer} */
const server = getServer();

const requestHandler = createRequestHandler({build});  
 
addEventListener("fetch", (event) => event.respondWith(handleRequest(event)));  
async function handleRequest(event) {  
  let response = await handleAsset(event, build, server);  
 
  if (!response) {  
    response = requestHandler(event);  
  }  
 
  return response;  
}
```

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/remix-compute-js/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/remix-server-runtime
Description: Remix Runtime for Fastly Compute
Latest version: 4.2.0

# Remix Runtime for Fastly Compute

This package implements the "Remix server runtime interface" that Remix runtime packages must conform to.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/remix-compute-js/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastly/serve-vercel-build-output
Description: Serve Vercel Build Output (v3) on Fastly Compute
Author: Katsuyuki Omuro
Latest version: 0.5.3

## Serve Vercel Build Output (v3) on Fastly Compute

> NOTE: `@fastly/serve-vercel-build-output` is provided as a Fastly Labs product. Visit the [Fastly Labs](https://www.fastlylabs.com/) site for terms of use.

This library's goal is to provide a runtime environment that executes output that targets the [Vercel Build Output API](https://vercel.com/docs/build-output-api/v3).

Vercel's Build Output API is a file-system-based specification for a directory structure that represents a Vercel deployment. It includes static files, functions, and a configuration file that expresses routing and internationalization rules.

While it's not (currently) possible to simulate it 100%, it is able to run a wide variety of programs, including those written for [Next.js v12.3 and v13.x](https://nextjs.org).

Current support includes:

* The standard `.vercel` directory containing output that targets Vercel's Build Output API
* Static files
* Functions that target the Vercel Edge Runtime
* The following features of config.json:
  * Routing
  * Overrides
  * Wildcards
  * Image Optimization

## Usage

This library is typically used with [`@fastly/next-compute-js`](https://github.com/fastly/next-compute-js) (v2).
See `@fastly/next-compute-js` for more details.

## Issues

If you encounter any non-security-related bug or unexpected behavior, please [file an issue][bug]
using the bug report template.

[bug]: https://github.com/fastly/serve-vercel-build-output/issues/new?labels=bug

### Security issues

Please see our [SECURITY.md](./SECURITY.md) for guidance on reporting security-related issues.

## License

[MIT](./LICENSE).
npm package: @fastmcp-me/3d-asset-processing-mcp
Description: 3D Asset Processing MCP Server
Author: geolibra
Latest version: 0.0.1-beta.5

[![Add to Cursor](https://fastmcp.me/badges/cursor_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)
[![Add to VS Code](https://fastmcp.me/badges/vscode_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)
[![Add to Claude](https://fastmcp.me/badges/claude_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)
[![Add to ChatGPT](https://fastmcp.me/badges/chatgpt_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)
[![Add to Codex](https://fastmcp.me/badges/codex_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)
[![Add to Gemini](https://fastmcp.me/badges/gemini_dark.svg)](https://fastmcp.me/MCP/Details/1357/3d-asset-processing)

# 3D Asset Processing MCP

A comprehensive MCP server for processing, validating, optimizing, and analyzing 3D models with glTF/GLB support.

## Features

- **Analysis**: Get detailed model statistics including geometry, materials, animations, and performance metrics
- **Validation**: Ensure 3D models meet standards using built-in checks
- **Basic Processing**: Convert between glTF/GLB formats using gltf-pipeline
- **Advanced Processing**: Apply Meshopt/Draco compression, texture optimization, and geometry processing using gltf-transform

## Installation

Add to your MCP client configuration:

```json
{
  "mcpServers": {
    "3d-asset-processing-mcp": {
      "command": "npx",
      "args": ["-y", "3d-asset-processing-mcp@0.0.1-beta.5"]
    }
  }
}
```

All dependencies (gltf-pipeline, gltf-transform) are included - no additional setup required.

## Available Tools

- **`analyze_model`**: Analyze 3D models and provide detailed statistics
- **`validate_model`**: Validate 3D models for compliance and compatibility
- **`gltf-pipeline-executor`**: Basic glTF operations (conversion, format upgrade, simple compression)
- **`gltf-transform-executor`**: Advanced glTF processing (Meshopt/Draco compression, texture optimization, geometry processing)

## Development

```bash
# Clone the repository
git clone git@github.com:GeoLibra/3d-asset-processing-mcp.git
cd 3d-asset-processing-mcp

# Install dependencies
npm install

# Build the project
npm run build

# debug mcp
"3d-asset-processing-mcp": {
  "command": "node",
  "args": [
    "/Users/hgis/myproject/3d-asset-processing-mcp/dist/server.js"
  ]
}
```

## debug mcp

```bash
npx @modelcontextprotocol/inspector
```

![Debug image](./images/debug.png)
## License

MIT