void 0.10.13 → 0.20.1

package/skills/void/docs/node_modules/void/node_modules/picocolors/README.md

@@ -1,21 +0,0 @@
-# picocolors
-
-The tiniest and the fastest library for terminal output formatting with ANSI colors.
-
-```javascript
-import pc from "picocolors"
-
-console.log(
-  pc.green(`How are ${pc.italic(`you`)} doing?`)
-)
-```
-
-- **No dependencies.**
-- **14 times** smaller and **2 times** faster than chalk.
-- Used by popular tools like PostCSS, SVGO, Stylelint, and Browserslist.
-- Node.js v6+ & browsers support. Support for both CJS and ESM projects.
-- TypeScript type declarations included.
-- [`NO_COLOR`](https://no-color.org/) friendly.
-
-## Docs
-Read **[full docs](https://github.com/alexeyraspopov/picocolors#readme)** on GitHub.

package/skills/void/docs/node_modules/void/node_modules/proper-lockfile/CHANGELOG.md

@@ -1,108 +0,0 @@
-# Change Log
-
-All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
-
-<a name="4.1.2"></a>
-## [4.1.2](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.1...v4.1.2) (2021-01-25)
-
-
-### Bug Fixes
-
-* fix node 14 updating graceful-fs ([#102](https://github.com/moxystudio/node-proper-lockfile/issues/102)) ([b0d988e](https://github.com/moxystudio/node-proper-lockfile/commit/b0d988e))
-
-
-
-<a name="4.1.1"></a>
-## [4.1.1](https://github.com/moxystudio/node-proper-lockfile/compare/v4.1.0...v4.1.1) (2019-04-03)
-
-
-### Bug Fixes
-
-* fix mtime precision on some filesystems ([#88](https://github.com/moxystudio/node-proper-lockfile/issues/88)) ([f266158](https://github.com/moxystudio/node-proper-lockfile/commit/f266158)), closes [#82](https://github.com/moxystudio/node-proper-lockfile/issues/82) [#87](https://github.com/moxystudio/node-proper-lockfile/issues/87)
-
-
-
-<a name="4.1.0"></a>
-# [4.1.0](https://github.com/moxystudio/node-proper-lockfile/compare/v4.0.0...v4.1.0) (2019-03-18)
-
-
-### Features
-
-* allow second precision in mtime comparison ([#78](https://github.com/moxystudio/node-proper-lockfile/issues/78)) ([b2816a6](https://github.com/moxystudio/node-proper-lockfile/commit/b2816a6))
-
-
-
-<a name="4.0.0"></a>
-# [4.0.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.2.0...v4.0.0) (2019-03-12)
-
-
-### Bug Fixes
-
-* fix typo in error message ([#68](https://github.com/moxystudio/node-proper-lockfile/issues/68)) ([b91cb55](https://github.com/moxystudio/node-proper-lockfile/commit/b91cb55))
-
-
-### Features
-
-* make staleness check more robust ([#74](https://github.com/moxystudio/node-proper-lockfile/issues/74)) ([9cc0973](https://github.com/moxystudio/node-proper-lockfile/commit/9cc0973)), closes [#71](https://github.com/moxystudio/node-proper-lockfile/issues/71) [/github.com/ipfs/js-ipfs-repo/issues/188#issuecomment-468682971](https://github.com//github.com/ipfs/js-ipfs-repo/issues/188/issues/issuecomment-468682971)
-
-
-### BREAKING CHANGES
-
-* We were marking the lock as compromised when system went into sleep or if the event loop was busy taking too long to run the internals timers, Now we keep track of the mtime updated by the current process, and if we lose some cycles in the update process but recover and the mtime is still ours we do not mark the lock as compromised.
-
-
-
-<a name="3.2.0"></a>
-# [3.2.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.1.0...v3.2.0) (2018-11-19)
-
-
-### Features
-
-* add lock path option ([#66](https://github.com/moxystudio/node-proper-lockfile/issues/66)) ([32f1b8d](https://github.com/moxystudio/node-proper-lockfile/commit/32f1b8d))
-
-
-
-<a name="3.1.0"></a>
-# [3.1.0](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.2...v3.1.0) (2018-11-15)
-
-
-### Bug Fixes
-
-* **package:** update retry to version 0.12.0 ([#50](https://github.com/moxystudio/node-proper-lockfile/issues/50)) ([d400b98](https://github.com/moxystudio/node-proper-lockfile/commit/d400b98))
-
-
-### Features
-
-* add signal exit ([#65](https://github.com/moxystudio/node-proper-lockfile/issues/65)) ([f20bc45](https://github.com/moxystudio/node-proper-lockfile/commit/f20bc45))
-
-
-
-<a name="3.0.2"></a>
-## [3.0.2](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.1...v3.0.2) (2018-01-30)
-
-
-
-<a name="3.0.1"></a>
-## [3.0.1](https://github.com/moxystudio/node-proper-lockfile/compare/v3.0.0...v3.0.1) (2018-01-20)
-
-
-### Bug Fixes
-
-* restore ability to use lockfile() directly ([0ef8fbc](https://github.com/moxystudio/node-proper-lockfile/commit/0ef8fbc))
-
-
-
-<a name="3.0.0"></a>
-# [3.0.0](https://github.com/moxystudio/node-proper-lockfile/compare/v2.0.1...v3.0.0) (2018-01-20)
-
-
-### Chores
-
-* update project to latest node lts ([b1d43e5](https://github.com/moxystudio/node-proper-lockfile/commit/b1d43e5))
-
-
-### BREAKING CHANGES
-
-* remove callback support
-* use of node lts language features such as object spread
-* compromised function in lock() has been moved to an option

package/skills/void/docs/node_modules/void/node_modules/proper-lockfile/README.md

@@ -1,183 +0,0 @@
-# proper-lockfile
-
-[![NPM version][npm-image]][npm-url] [![Downloads][downloads-image]][npm-url] [![Build Status][travis-image]][travis-url] [![Coverage Status][codecov-image]][codecov-url] [![Dependency status][david-dm-image]][david-dm-url] [![Dev Dependency status][david-dm-dev-image]][david-dm-dev-url]
-
-[npm-url]:https://npmjs.org/package/proper-lockfile
-[downloads-image]:https://img.shields.io/npm/dm/proper-lockfile.svg
-[npm-image]:https://img.shields.io/npm/v/proper-lockfile.svg
-[travis-url]:https://travis-ci.org/moxystudio/node-proper-lockfile
-[travis-image]:https://img.shields.io/travis/moxystudio/node-proper-lockfile/master.svg
-[codecov-url]:https://codecov.io/gh/moxystudio/node-proper-lockfile
-[codecov-image]:https://img.shields.io/codecov/c/github/moxystudio/node-proper-lockfile/master.svg
-[david-dm-url]:https://david-dm.org/moxystudio/node-proper-lockfile
-[david-dm-image]:https://img.shields.io/david/moxystudio/node-proper-lockfile.svg
-[david-dm-dev-url]:https://david-dm.org/moxystudio/node-proper-lockfile?type=dev
-[david-dm-dev-image]:https://img.shields.io/david/dev/moxystudio/node-proper-lockfile.svg
-
-An inter-process and inter-machine lockfile utility that works on a local or network file system.
-
-
-## Installation
-
-`$ npm install proper-lockfile`
-
-
-## Design
-
-There are various ways to achieve [file locking](http://en.wikipedia.org/wiki/File_locking).
-
-This library utilizes the `mkdir` strategy which works atomically on any kind of file system, even network based ones.
-The lockfile path is based on the file path you are trying to lock by suffixing it with `.lock`.
-
-When a lock is successfully acquired, the lockfile's `mtime` (modified time) is periodically updated to prevent staleness. This allows to effectively check if a lock is stale by checking its `mtime` against a stale threshold. If the update of the mtime fails several times, the lock might be compromised. The `mtime` is [supported](http://en.wikipedia.org/wiki/Comparison_of_file_systems) in almost every `filesystem`.
-
-
-### Comparison
-
-This library is similar to [lockfile](https://github.com/isaacs/lockfile) but the latter has some drawbacks:
-
-- It relies on `open` with `O_EXCL` flag which has problems in network file systems. `proper-lockfile` uses `mkdir` which doesn't have this issue.
-
-> O_EXCL is broken on NFS file systems; programs which rely on it for performing locking tasks will contain a race condition.
-
-- The lockfile staleness check is done via `ctime` (creation time) which is unsuitable for long running processes. `proper-lockfile` constantly updates lockfiles `mtime` to do proper staleness check.
-
-- It does not check if the lockfile was compromised which can lead to undesirable situations. `proper-lockfile` checks the lockfile when updating the `mtime`.
-
-- It has a default value of `0` for the stale option which isn't good because any crash or process kill that the package can't handle gracefully will leave the lock active forever.
-
-
-### Compromised
-
-`proper-lockfile` does not detect cases in which:
-
-- A `lockfile` is manually removed and someone else acquires the lock right after
-- Different `stale`/`update` values are being used for the same file, possibly causing two locks to be acquired on the same file
-
-`proper-lockfile` detects cases in which:
-
-- Updates to the `lockfile` fail
-- Updates take longer than expected, possibly causing the lock to become stale for a certain amount of time
-
-
-As you see, the first two are a consequence of bad usage. Technically, it was possible to detect the first two but it would introduce complexity and eventual race conditions.
-
-
-## Usage
-
-### .lock(file, [options])
-
-Tries to acquire a lock on `file` or rejects the promise on error.
-
-If the lock succeeds, a `release` function is provided that should be called when you want to release the lock. The `release` function also rejects the promise on error (e.g. when the lock was already compromised).
-
-Available options:
-
-- `stale`: Duration in milliseconds in which the lock is considered stale, defaults to `10000` (minimum value is `5000`)
-- `update`: The interval in milliseconds in which the lockfile's `mtime` will be updated, defaults to `stale/2` (minimum value is `1000`, maximum value is `stale/2`)
-- `retries`: The number of retries or a [retry](https://www.npmjs.org/package/retry) options object, defaults to `0`
-- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
-- `fs`: A custom fs to use, defaults to `graceful-fs`
-- `onCompromised`: Called if the lock gets compromised, defaults to a function that simply throws the error which will probably cause the process to die
-- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
-
-
-```js
-const lockfile = require('proper-lockfile');
-
-lockfile.lock('some/file')
-.then((release) => {
-    // Do something while the file is locked
-
-    // Call the provided release function when you're done,
-    // which will also return a promise
-    return release();
-})
-.catch((e) => {
-    // either lock could not be acquired
-    // or releasing it failed
-    console.error(e)
-});
-
-// Alternatively, you may use lockfile('some/file') directly.
-```
-
-
-### .unlock(file, [options])
-
-Releases a previously acquired lock on `file` or rejects the promise on error.
-
-Whenever possible you should use the `release` function instead (as exemplified above). Still there are cases in which it's hard to keep a reference to it around code. In those cases `unlock()` might be handy.
-
-Available options:
-
-- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
-- `fs`: A custom fs to use, defaults to `graceful-fs`
-- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
-
-
-```js
-const lockfile = require('proper-lockfile');
-
-lockfile.lock('some/file')
-.then(() => {
-    // Do something while the file is locked
-
-    // Later..
-    return lockfile.unlock('some/file');
-});
-```
-
-### .check(file, [options])
-
-Check if the file is locked and its lockfile is not stale, rejects the promise on error.
-
-Available options:
-
-- `stale`: Duration in milliseconds in which the lock is considered stale, defaults to `10000` (minimum value is `5000`)
-- `realpath`: Resolve symlinks using realpath, defaults to `true` (note that if `true`, the `file` must exist previously)
-- `fs`: A custom fs to use, defaults to `graceful-fs`
-- `lockfilePath`: Custom lockfile path. e.g.: If you want to lock a directory and create the lock file inside it, you can pass `file` as `<dir path>` and `options.lockfilePath` as `<dir path>/dir.lock`
-
-
-```js
-const lockfile = require('proper-lockfile');
-
-lockfile.check('some/file')
-.then((isLocked) => {
-    // isLocked will be true if 'some/file' is locked, false otherwise
-});
-```
-
-### .lockSync(file, [options])
-
-Sync version of `.lock()`.   
-Returns the `release` function or throws on error.
-
-### .unlockSync(file, [options])
-
-Sync version of `.unlock()`.   
-Throws on error.
-
-### .checkSync(file, [options])
-
-Sync version of `.check()`.
-Returns a boolean or throws on error.
-
-
-## Graceful exit
-
-`proper-lockfile` automatically removes locks if the process exits, except if the process is killed with SIGKILL or it crashes due to a VM fatal error (e.g.: out of memory).
-
-
-## Tests
-
-`$ npm test`   
-`$ npm test -- --watch` during development
-
-The test suite is very extensive. There's even a stress test to guarantee exclusiveness of locks.
-
-
-## License
-
-Released under the [MIT License](https://www.opensource.org/licenses/mit-license.php).

package/skills/void/docs/node_modules/void/node_modules/tinyglobby/README.md

@@ -1,25 +0,0 @@
-# tinyglobby
-
-[![npm version](https://img.shields.io/npm/v/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
-[![weekly downloads](https://img.shields.io/npm/dw/tinyglobby.svg?maxAge=3600)](https://npmjs.com/package/tinyglobby)
-
-A fast and minimal alternative to globby and fast-glob, meant to behave the same way.
-
-Both globby and fast-glob present some behavior no other globbing lib has,
-which makes it hard to manually replace with something smaller and better.
-
-This library uses only two subdependencies, compared to `globby`'s [23](https://npmgraph.js.org/?q=globby@16.2.0)
-and `fast-glob`'s [17](https://npmgraph.js.org/?q=fast-glob@3.3.3).
-
-## Usage
-
-```js
-import { glob, globSync } from 'tinyglobby';
-
-await glob(['files/*.ts', '!**/*.d.ts'], { cwd: 'src' });
-globSync('src/**/*.ts', { ignore: '**/*.d.ts' });
-```
-
-## Documentation
-
-Visit https://superchupu.dev/tinyglobby to read the full documentation.

package/skills/void/docs/node_modules/void/node_modules/valibot/LICENSE.md

@@ -1,9 +0,0 @@
-MIT License
-
-Copyright (c) Fabian Hiller
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/skills/void/docs/node_modules/void/node_modules/valibot/README.md

@@ -1,94 +0,0 @@
-![Valibot Logo](https://github.com/open-circle/valibot/blob/main/valibot.jpg?raw=true)
-
-# Valibot
-
-[![License: MIT][license-image]][license-url]
-[![CI][ci-image]][ci-url]
-[![NPM version][npm-image]][npm-url]
-[![Downloads][downloads-image]][npm-url]
-[![JSR version][jsr-image]][jsr-url]
-[![Discord][discord-image]][discord-url]
-
-Hello, I am Valibot and I would like to help you validate data easily using a schema. No matter if it is incoming data on a server, a form or even configuration files. I have no dependencies and can run in any JavaScript environment.
-
-> I highly recommend you read the [announcement post](https://www.builder.io/blog/introducing-valibot), and if you are a nerd like me, the [bachelor's thesis](https://valibot.dev/thesis.pdf) I am based on.
-
-## Highlights
-
-- Fully type safe with static type inference
-- Small bundle size starting at less than 700 bytes
-- Validate everything from strings to complex objects
-- Open source and fully tested with 100 % coverage
-- Many transformation and validation actions included
-- Well structured source code without dependencies
-- Minimal, readable and well thought out API
-
-## Example
-
-First you create a schema that describes a structured data set. A schema can be compared to a type definition in TypeScript. The big difference is that TypeScript types are "not executed" and are more or less a DX feature. A schema on the other hand, apart from the inferred type definition, can also be executed at runtime to guarantee the type safety of unknown data.
-
-<!-- prettier-ignore -->
-```ts
-import * as v from 'valibot'; // 1.31 kB
-
-// Create login schema with email and password
-const LoginSchema = v.object({
-  email: v.pipe(v.string(), v.email()),
-  password: v.pipe(v.string(), v.minLength(8)),
-});
-
-// Infer output TypeScript type of login schema as
-// { email: string; password: string }
-type LoginData = v.InferOutput<typeof LoginSchema>;
-
-// Throws error for email and password
-const output1 = v.parse(LoginSchema, { email: '', password: '' });
-
-// Returns data as { email: string; password: string }
-const output2 = v.parse(LoginSchema, {
-  email: 'jane@example.com',
-  password: '12345678',
-});
-```
-
-Apart from `parse` I also offer a non-exception-based API with `safeParse` and a type guard function with `is`. You can read more about it [here](https://valibot.dev/guides/parse-data/).
-
-## Comparison
-
-Instead of relying on a few large functions with many methods, my API design and source code is based on many small and independent functions, each with just a single task. This modular design has several advantages.
-
-For example, this allows a bundler to use the import statements to remove code that is not needed. This way, only the code that is actually used gets into your production build. This can reduce the bundle size by up to 95 % compared to [Zod](https://zod.dev/).
-
-In addition, it allows you to easily extend my functionality with external code and makes my source code more robust and secure because the functionality of the individual functions can be tested much more easily through unit tests.
-
-> Coming from [Zod](https://zod.dev/)? Read our [migration article](https://valibot.dev/blog/why-migrate-to-valibot/) to see the benefits of Valibot, and use our [migration guide](https://valibot.dev/guides/migrate-from-zod/) to migrate your schemas with confidence.
-
-## Partners
-
-Thanks to our partners who support my development! [Join them](https://github.com/sponsors/fabian-hiller) and contribute to the sustainability of open source software!
-
-![Partners of Valibot](https://github.com/open-circle/valibot/blob/main/partners.webp?raw=true)
-
-## Credits
-
-My friend [Fabian](https://github.com/fabian-hiller) created me as part of his [bachelor thesis](https://valibot.dev/thesis.pdf) at [Stuttgart Media University](https://www.hdm-stuttgart.de/en/), supervised by Walter Kriha, [Miško Hevery](https://github.com/mhevery) and [Ryan Carniato](https://github.com/ryansolid). My role models also include [Colin McDonnell](https://github.com/colinhacks), who had a big influence on my API design with [Zod](https://zod.dev/).
-
-## Feedback
-
-Find a bug or have an idea how to improve my code? Please fill out an [issue](https://github.com/open-circle/valibot/issues/new). Together we can make the library even better!
-
-## License
-
-I am completely free and licensed under the [MIT license](https://github.com/open-circle/valibot/blob/main/LICENSE.md). But if you like, you can feed me with a star on [GitHub](https://github.com/open-circle/valibot).
-
-[license-image]: https://img.shields.io/badge/License-MIT-brightgreen.svg?style=flat-square
-[license-url]: https://opensource.org/licenses/MIT
-[ci-image]: https://img.shields.io/github/actions/workflow/status/open-circle/valibot/ci.yml?branch=main&logo=github&style=flat-square
-[ci-url]: https://github.com/open-circle/valibot/actions/workflows/ci.yml
-[npm-image]: https://img.shields.io/npm/v/valibot.svg?style=flat-square
-[npm-url]: https://npmjs.org/package/valibot
-[downloads-image]: https://img.shields.io/npm/dm/valibot.svg?style=flat-square
-[jsr-image]: https://jsr.io/badges/@valibot/valibot?style=flat-square
-[jsr-url]: https://jsr.io/@valibot/valibot
-[discord-image]: https://img.shields.io/discord/1252985447273992222?label=Discord&style=flat-square
-[discord-url]: https://discord.gg/tkMjQACf2P

package/skills/void/docs/node_modules/void/node_modules/vite-plus/AGENTS.md

@@ -1,16 +0,0 @@
-<!--VITE PLUS START-->
-
-# Using Vite+, the Unified Toolchain for the Web
-
-This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called `vp`. Vite+ is distinct from Vite, and it invokes Vite through `vp dev` and `vp build`. Run `vp help` to print a list of commands and `vp <command> --help` for information about a specific command.
-
-Docs are local at `node_modules/vite-plus/docs` or online at https://viteplus.dev/guide/.
-
-## Review Checklist
-
-- [ ] Run `vp install` after pulling remote changes and before getting started.
-- [ ] Run `vp check` and `vp test` to format, lint, type check and test changes.
-- [ ] Check if there are `vite.config.ts` tasks or `package.json` scripts necessary for validation, run via `vp run <script>`.
-- [ ] If setup, runtime, or package-manager behavior looks wrong, run `vp env doctor` and include its output when asking for help.
-
-<!--VITE PLUS END-->