![\"npm](\"https://badge.fury.io/js/@fast-check%2Fava.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fava\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fava.svg\")
\n\n---\n\n## Getting Started\n\nInstall `@fast-check/ava`:\n\n```bash\nnpm install --save-dev @fast-check/ava\n```\n\nIn order to work properly, `@fast-check/ava` requires `ava` to be installed.\n\n## Example\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntestProp('should detect the substring', [fc.string(), fc.string(), fc.string()], (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n});\n```\n\nThe property is passed [AVA's `t` argument](https://github.com/avajs/ava/blob/main/docs/02-execution-context.md#execution-context-t-argument) as its first parameter, and the value of each arbitrary for the current test case for the rest of the parameters.\n\n`@fast-check/ava` supports all of [AVA's assertions](https://github.com/avajs/ava/blob/main/docs/03-assertions.md#assertions) and like AVA, it supports synchronous and asynchronous functions, including promises, observables, and callbacks. See [AVA's documentation](https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#declaring-test) for more information.\n\nβ οΈ **WARNING:** When relying on `@fast-check/ava`, returning `true` or `false` in your predicates is not taken into account. The library wants assertions or plans to be defined as `ava` itself does. Nonetheless you can still use primitives such as `fc.pre` to cut runs at the middle if some invariants are unmeet: the started plan (if any) will just be ignored.\n\n## Advanced\n\n### `fast-check` Parameters\n\n`testProp` accepts an optional `fc.Parameters` for forwarding custom parameters to `fast-check` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should detect the substring',\n [fc.string(), fc.string(), fc.string()],\n (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n },\n { numRuns: 10 }, // Example of parameters\n);\n```\n\n### AVA Modifiers\n\n`@fast-check/ava` also comes with [`.only`], [`.serial`] [`.skip`], and [`.failing`] modifiers from AVA.\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should replay the test for the seed 4242',\n [fc.nat(), fc.nat()],\n (t, a, b) => {\n t.is(a + b, b + a);\n },\n { seed: 4242 },\n);\n\ntestProp.skip('should be skipped', [fc.string()], (t, text) => {\n t.is([...text].length, text.length);\n});\n```\n\n[`.only`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-specific-tests\n[`.serial`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-tests-serially\n[`.skip`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#skipping-tests\n[`.failing`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#failing-tests\n\n### AVA `before`/`after` Hooks\n\n`@fast-check/ava` exposes AVA's `before`/`after` [hooks]:\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp.before((t) => {\n connectToDatabase();\n});\n\ntestProp();\n// ... omitted for brevity\n\ntestProp.after((t) => {\n closeDatabaseConnection();\n});\n```\n\n[hooks]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#before--after-hooks\n\n### AVA Execution Context\n\n`@fast-check/ava` mirror's AVA's procedure for customizing the test [execution context]:\n\n```typescript\nimport { fc, testProp as anyTestProp, PropertyTestInterface } from '@fast-check/ava';\n\ntype TestContext = {\n state: string;\n};\n\nconst testProp = anyTestProp as PropertyTestInterface![\"fast-check](\"https://fast-check.dev/assets/images/logo.png\"){kind=logo}
\n\nProperty based testing framework for JavaScript/TypeScript\n
\n\n\n ![\"Build](\"https://github.com/dubzzz/fast-check/actions/workflows/build-status.yml/badge.svg?branch=main\"){kind=icon}
\n ![\"npm](\"https://badge.fury.io/js/fast-check.svg\"){kind=icon}
\n ![\"monthly](\"https://img.shields.io/npm/dm/fast-check\")
![](\"https://img.shields.io/badge/-Documentation-%23282ea9.svg\" "\\"Documentation\\""){kind=icon}
\n
\n ![\"Coverage](\"https://codecov.io/gh/dubzzz/fast-check/branch/main/graph/badge.svg\"){kind=icon}
\n ![\"Package](\"https://packagequality.com/shield/fast-check.svg\")
\n \n
\n
\n ![\"PRs](\"https://img.shields.io/badge/PRs-welcome-brightgreen.svg\"){kind=icon}
\n ![\"License\"](\"https://img.shields.io/npm/l/fast-check.svg\")
\n
![\"all](\"https://raw.githubusercontent.com/dubzzz/sponsors-svg/main/sponsorkit/sponsors.svg\")
\n\nYou can also become one of them by contributing via [GitHub Sponsors](https://github.com/sponsors/dubzzz) or [OpenCollective](https://opencollective.com/fast-check/contribute).\n","packages/jest/README.md":"# `@fast-check/jest`\n\n\n\nBring the power of property based testing framework `fast-check` into Jest.\n`@fast-check/jest` simplifies the integration of `fast-check` into Jest testing framework.\n\n![\"npm](\"https://badge.fury.io/js/@fast-check%2Fjest.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fjest\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fjest.svg\")
\n\n---\n\n## Getting Started\n\nInstall `@fast-check/jest`:\n\n```bash\nnpm install --save-dev @fast-check/jest\n```\n\nIn order to work properly, `@fast-check/jest` requires `jest` to be installed.\n\nWe also highly recommend users to launch their tests using the `--show-seed` option provided by Jest. It ensures Jest will always print the seed by itself (requires Jest β₯29.2.0).\n\n```sh\njest --show-seed\n```\n\n## Example\n\n```javascript\nimport { test, fc } from '@fast-check/jest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// Or the exact same test but based on named parameters\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nThe `it` and `test` functions returned by `@fast-check/jest` are just enriched versions of the ones coming from `jest` itself. They both come with `.prop`.\n\nPlease note that the properties accepted by `@fast-check/jest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances). In other words, the predicate passed as the last argument can be asynchronous.\n\n**Remark:** `it` and `test` have been introduced in 1.4.0. You have to refer to [Deprecated API](#deprecated-api) if you are using a version of `@fast-check/jest` <1.4.0.\n\n## Advanced\n\n### Support for variations of `test` and `it`\n\nIf you want to forward custom parameters to `fast-check`, `test.prop` and its variants accept an optional `fc.Parameters` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n`@fast-check/jest` also comes with support for `.only`, `.skip`, `.todo` and `.concurrent` from `jest`. It also accepts more complex ones such as `.concurrent.failing` or `.concurrent.only.failing`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/jest';\n\n// With custom `fc.Parameters`, here { seed: 4242 }\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\n// With .skip\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\n// With it version\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n### Experimental worker-based runner\n\n**The following feature is experimental!** When used it makes runners able to kill long running synchonous code. Meaning that it will make fast-check able to kill infinite loops blocking the main thread. So far, the feature does not fully support transformations performed via transform steps defined with jest.\n\nThe CommonJS approach would be:\n\n```js\nconst { init, fc } = require('@fast-check/jest/worker');\nconst { pathToFileURL } = require('node:url');\n\nconst { test, expect } = init(pathToFileURL(__filename));\n// can also be passed options such as isolationLevel: init(pathToFileURL(__filename), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nThe ES Modules approach would be:\n\n```js\nimport { init, fc } from '@fast-check/jest/worker';\n\nconst { test, expect } = await init(new URL(import.meta.url));\n// can also be passed options such as isolationLevel: init(new URL(import.meta.url), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nβ οΈ Do not forget to add the `await` before `init` for the ES Module version!\n\n#### Extra setup for `@fast-check/worker` 0.6.0 and later\n\nSince `@fast-check/worker` is an ESM-only package, running it under Jest in CommonJS mode requires `babel-jest` to transpile it. Install the following dependencies:\n\n```bash\nnpm install --save-dev babel-jest @babel/core @babel/preset-env\n```\n\nThen add a `babel.config.cjs` at the root of your project:\n\n```js\nmodule.exports = {\n presets: [['@babel/preset-env', { targets: { node: 'current' }, modules: 'commonjs' }]],\n};\n```\n\nAnd update your Jest configuration to use `babel-jest` while excluding `@fast-check/worker` from the ignore patterns:\n\n```js\nmodule.exports = {\n transform: {\n '^.+\\\\.[t|j]sx?$': 'babel-jest',\n },\n transformIgnorePatterns: ['/node_modules/(?!(?:@fast-check/worker)/)'],\n};\n```\n\nThis ensures `@fast-check/worker` gets transpiled to CommonJS by Babel instead of being skipped. Without it, Jest will fail to load the ESM-only package.\n\nFor ES Modules mode, no extra setup is needed β just make sure to run Jest with `--experimental-vm-modules`:\n\n```bash\nnode --experimental-vm-modules node_modules/jest/bin/jest.js\n```\n\n## Minimal requirements\n\n| @fast-check/jest | jest | fast-check | node |\n| ---------------- | --------------------------------------- | ---------- | ------------------------------------------------------------------------------------- |\n| ^2.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n| ^1.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n\n- (1) any version of `jest` should be greater or equal than 26.5.0 if you are using `commonjs`\n- (2) in order to use `esm` build, you may need to enable experimental features of node, see [here](https://github.com/dubzzz/fast-check/blob/main/packages/test-jest-bundle-esm/package.json)\n- (3) >=14.15.0 is the minimal requirements for `jest`, >=12.17.0 is the one for `@fast-check/jest`\n- (4) timeout defined on jest might not be properly applied to fast-check for node 18 (until 18.17.0) and node 19, see [#4004](https://github.com/dubzzz/fast-check/pull/4004)\n","packages/packaged/README.md":"# `@fast-check/packaged`\n\nUtility package removing any files that will not be part of the final bundle published to npm registry\n\n![\"npm](\"https://badge.fury.io/js/@fast-check%2Fpackaged.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fpackaged\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fpackaged.svg\")
\n\n---\n\n## Why?\n\nWhen publishing packages to npm registry, it is quite easy to forget about some files. It also happens many times that we want somehow to check the packaged bundle in some of our tests but totally forget that some files have not been added to the bundle and so that the final user will actually never be able to run this code.\n\nThis package mostly try to prevent this issue. It can easily be used in monorepos to emulate the bundled package when used against other packages of the monorepo to make sure others do not depend on internals or non published stuff.\n\n## Easy to use\n\nRun the following command at the root of your package to drop any file that will not make it in the final bundle published to npm.\n\n```bash\n# With npm\nnpx -p @fast-check/packaged packaged\n# With pnpm\npnpm --package=@fast-check/packaged dlx packaged\n# With yarn\nyarn dlx -p @fast-check/packaged packaged\n```\n\nβ οΈ You may want to try with `--dry-run` flag first to give it a try.\n\nIt also comes with some extra flags:\n\n- `--dry-run`: do not drop any file or directory from the file system and only print what would have been removed\n- `--keep ![\"npm](\"https://badge.fury.io/js/@fast-check%2Fpoisoning.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fpoisoning\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fpoisoning.svg\")
\n\n---\n\n## Why?\n\nIn JavaScript, \"prototype poisoning\" is one of the most common source for CVEs or zero days. It allows attackers to change the behaviour of some defaults like `Array.prototype.map`, `Map`, `Set`... so that they behave differently and can be leveraged for evil stuffs. This package can be used in addition to `fast-check` in order to detect poisoning that may occur during your property based tests.\n\n## Easy to use\n\nThe package comes with:\n\n- `assertNoPoisoning`: assert that the defaults known when first importing the package in your code have not been changed\n- `restoreGlobals`: restore the defaults so that any change that could have been detected by `assertNoPoisoning` will be resolved\n\n## Minimal requirements\n\n- Node β₯20.19.0\n","packages/vitest/README.md":"# `@fast-check/vitest`\n\n\n\nBring the power of property based testing framework `fast-check` into Vitest.\n`@fast-check/vitest` simplifies the integration of `fast-check` into Vitest.\n\n![\"npm](\"https://badge.fury.io/js/@fast-check%2Fvitest.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fvitest\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fvitest.svg\")
\n\n---\n\n## Getting Started\n\nInstall `@fast-check/vitest`:\n\n```bash\nnpm install --save-dev @fast-check/vitest\n```\n\nIn order to work properly, `@fast-check/vitest` requires `vitest` to be installed.\n\n## Examples\n\nThe library comes with two modes, both powered by fast-check:\n\n- One-time random mode β A lightweight approach that introduces controlled randomness into your tests while keeping runs reproducible.\n- Property-based testing mode β A full-fledged property-based testing approach leveraging the full capabilities of fast-check.\n\n### One-time random mode\n\nThis mode extends Vitest's default `test` and `it` functions, allowing you to introduce controlled randomness into your tests while ensuring failures remain reproducible. This makes it easier to debug flaky tests and avoid irreproducible failures due to randomness.\n\nUnlike property-based testing, this mode does not run tests multiple times or attempt shrinking when failures occur. Instead, it provides a determistic way to introduce randomness when needed.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\nimport { expect } from 'vitest';\n\n// You can provide a fixed seed to force a replay by adding this line:\n// >> fc.configureGlobal({ seed })\n// Eventually you can disable shrinking capabilities with:\n// >> fc.configureGlobal({ endOnFailure: false })\n// >> // or combine it with the one above if you need both\n\ntest('test relying on randomness', ({ g }) => {\n // Arrange\n const user = {\n firstName: g(fc.string),\n lastName: g(fc.string),\n };\n\n // Act\n const displayName = computeDisplayName(user);\n\n // Assert\n expect(displayName).toContain(user.firstName);\n});\n\ntest('test not relying on randomness', () => {\n // your test\n});\n```\n\n### Full property-based mode\n\nFor more extensive testing, `@fast-check/vitest` also provides full support for property-based testing. This mode enables exhaustive, randomized testing by generating a variety of inputs and detecting edge cases automatically.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// same property but using named values\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nPlease note that the properties accepted by `@fast-check/vitest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances).\n\n### Seamless integration with Vitest's `beforeEach` / `afterEach`\n\nVitest's `beforeEach` and `afterEach` hooks are natively integrated into predicates. They are called respectively before and after each execution of the predicate. If a predicate runs _n_ times, `beforeEach` will be called _n_ times before it and `afterEach` _n_ times after it. The only caveat is that cleanup functions returned by `beforeEach` on the first predicate execution are deferred until the end of the test, as they are handled by vitest's own teardown mechanism. All other cleanups run between predicate executions as expected.\n\n### Advanced\n\nIf you want to forward custom parameters to fast-check, `test.prop` accepts an optional `fc.Parameters` ([more](https://github.com/dubzzz/fast-check/blob/main/documentation/1-Guides/Runners.md#runners)).\n\n`@fast-check/vitest` also comes with `.only`, `.skip`, `.todo` and `.concurrent` from vitest. It also accepts more complex ones such as `.concurrent.skip`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/vitest';\n\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n## Minimal requirements\n\n| @fast-check/vitest | vitest | fast-check | Node |\n| ------------------ | ------------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------- |\n| **0.4** | ^4.1.0 \\|\\| ^5.0.0 | ^3.0.0 \\|\\| ^4.0.0 | β₯20.19.0(2) (Vitest 4)![\"npm](\"https://badge.fury.io/js/@fast-check%2Fworker.svg\"){kind=icon}
\n![\"monthly](\"https://img.shields.io/npm/dm/@fast-check%2Fworker\")
\n![\"License\"](\"https://img.shields.io/npm/l/@fast-check%2Fworker.svg\")
\n\n---\n\n## Why?\n\n`fast-check` alone is great but what if it led your code into an infinite and synchronous loop for such inputs? In such case, it would neither be able to shrink the issue, nor to report any for you as the single threaded philosophy at the root of JavaScript will prevent it from anything except waiting for the main thread to come back.\n\nThis package tends to provide a way to run easily your properties within dedicated workers automatically spawed by it.\n\n## Example\n\nHere are some of the changes you will have to do:\n\n- hoist properties so that they get declared on the root scope\n- replace `fc.property` by `property` coming from `propertyFor(\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/ava`:\n\n```bash\nnpm install --save-dev @fast-check/ava\n```\n\nIn order to work properly, `@fast-check/ava` requires `ava` to be installed.\n\n## Example\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntestProp('should detect the substring', [fc.string(), fc.string(), fc.string()], (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n});\n```\n\nThe property is passed [AVA's `t` argument](https://github.com/avajs/ava/blob/main/docs/02-execution-context.md#execution-context-t-argument) as its first parameter, and the value of each arbitrary for the current test case for the rest of the parameters.\n\n`@fast-check/ava` supports all of [AVA's assertions](https://github.com/avajs/ava/blob/main/docs/03-assertions.md#assertions) and like AVA, it supports synchronous and asynchronous functions, including promises, observables, and callbacks. See [AVA's documentation](https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#declaring-test) for more information.\n\nβ οΈ **WARNING:** When relying on `@fast-check/ava`, returning `true` or `false` in your predicates is not taken into account. The library wants assertions or plans to be defined as `ava` itself does. Nonetheless you can still use primitives such as `fc.pre` to cut runs at the middle if some invariants are unmeet: the started plan (if any) will just be ignored.\n\n## Advanced\n\n### `fast-check` Parameters\n\n`testProp` accepts an optional `fc.Parameters` for forwarding custom parameters to `fast-check` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should detect the substring',\n [fc.string(), fc.string(), fc.string()],\n (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n },\n { numRuns: 10 }, // Example of parameters\n);\n```\n\n### AVA Modifiers\n\n`@fast-check/ava` also comes with [`.only`], [`.serial`] [`.skip`], and [`.failing`] modifiers from AVA.\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should replay the test for the seed 4242',\n [fc.nat(), fc.nat()],\n (t, a, b) => {\n t.is(a + b, b + a);\n },\n { seed: 4242 },\n);\n\ntestProp.skip('should be skipped', [fc.string()], (t, text) => {\n t.is([...text].length, text.length);\n});\n```\n\n[`.only`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-specific-tests\n[`.serial`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-tests-serially\n[`.skip`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#skipping-tests\n[`.failing`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#failing-tests\n\n### AVA `before`/`after` Hooks\n\n`@fast-check/ava` exposes AVA's `before`/`after` [hooks]:\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp.before((t) => {\n connectToDatabase();\n});\n\ntestProp();\n// ... omitted for brevity\n\ntestProp.after((t) => {\n closeDatabaseConnection();\n});\n```\n\n[hooks]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#before--after-hooks\n\n### AVA Execution Context\n\n`@fast-check/ava` mirror's AVA's procedure for customizing the test [execution context]:\n\n```typescript\nimport { fc, testProp as anyTestProp, PropertyTestInterface } from '@fast-check/ava';\n\ntype TestContext = {\n state: string;\n};\n\nconst testProp = anyTestProp as PropertyTestInterface\n\nProperty based testing framework for JavaScript/TypeScript\n
\n\n\n \n \n \n
\n \n \n \n
\n
\n \n \n
\n\nYou can also become one of them by contributing via [GitHub Sponsors](https://github.com/sponsors/dubzzz) or [OpenCollective](https://opencollective.com/fast-check/contribute).\n","packages/jest/README.md":"# `@fast-check/jest`\n\n\n\nBring the power of property based testing framework `fast-check` into Jest.\n`@fast-check/jest` simplifies the integration of `fast-check` into Jest testing framework.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/jest`:\n\n```bash\nnpm install --save-dev @fast-check/jest\n```\n\nIn order to work properly, `@fast-check/jest` requires `jest` to be installed.\n\nWe also highly recommend users to launch their tests using the `--show-seed` option provided by Jest. It ensures Jest will always print the seed by itself (requires Jest β₯29.2.0).\n\n```sh\njest --show-seed\n```\n\n## Example\n\n```javascript\nimport { test, fc } from '@fast-check/jest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// Or the exact same test but based on named parameters\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nThe `it` and `test` functions returned by `@fast-check/jest` are just enriched versions of the ones coming from `jest` itself. They both come with `.prop`.\n\nPlease note that the properties accepted by `@fast-check/jest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances). In other words, the predicate passed as the last argument can be asynchronous.\n\n**Remark:** `it` and `test` have been introduced in 1.4.0. You have to refer to [Deprecated API](#deprecated-api) if you are using a version of `@fast-check/jest` <1.4.0.\n\n## Advanced\n\n### Support for variations of `test` and `it`\n\nIf you want to forward custom parameters to `fast-check`, `test.prop` and its variants accept an optional `fc.Parameters` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n`@fast-check/jest` also comes with support for `.only`, `.skip`, `.todo` and `.concurrent` from `jest`. It also accepts more complex ones such as `.concurrent.failing` or `.concurrent.only.failing`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/jest';\n\n// With custom `fc.Parameters`, here { seed: 4242 }\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\n// With .skip\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\n// With it version\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n### Experimental worker-based runner\n\n**The following feature is experimental!** When used it makes runners able to kill long running synchonous code. Meaning that it will make fast-check able to kill infinite loops blocking the main thread. So far, the feature does not fully support transformations performed via transform steps defined with jest.\n\nThe CommonJS approach would be:\n\n```js\nconst { init, fc } = require('@fast-check/jest/worker');\nconst { pathToFileURL } = require('node:url');\n\nconst { test, expect } = init(pathToFileURL(__filename));\n// can also be passed options such as isolationLevel: init(pathToFileURL(__filename), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nThe ES Modules approach would be:\n\n```js\nimport { init, fc } from '@fast-check/jest/worker';\n\nconst { test, expect } = await init(new URL(import.meta.url));\n// can also be passed options such as isolationLevel: init(new URL(import.meta.url), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nβ οΈ Do not forget to add the `await` before `init` for the ES Module version!\n\n#### Extra setup for `@fast-check/worker` 0.6.0 and later\n\nSince `@fast-check/worker` is an ESM-only package, running it under Jest in CommonJS mode requires `babel-jest` to transpile it. Install the following dependencies:\n\n```bash\nnpm install --save-dev babel-jest @babel/core @babel/preset-env\n```\n\nThen add a `babel.config.cjs` at the root of your project:\n\n```js\nmodule.exports = {\n presets: [['@babel/preset-env', { targets: { node: 'current' }, modules: 'commonjs' }]],\n};\n```\n\nAnd update your Jest configuration to use `babel-jest` while excluding `@fast-check/worker` from the ignore patterns:\n\n```js\nmodule.exports = {\n transform: {\n '^.+\\\\.[t|j]sx?$': 'babel-jest',\n },\n transformIgnorePatterns: ['/node_modules/(?!(?:@fast-check/worker)/)'],\n};\n```\n\nThis ensures `@fast-check/worker` gets transpiled to CommonJS by Babel instead of being skipped. Without it, Jest will fail to load the ESM-only package.\n\nFor ES Modules mode, no extra setup is needed β just make sure to run Jest with `--experimental-vm-modules`:\n\n```bash\nnode --experimental-vm-modules node_modules/jest/bin/jest.js\n```\n\n## Minimal requirements\n\n| @fast-check/jest | jest | fast-check | node |\n| ---------------- | --------------------------------------- | ---------- | ------------------------------------------------------------------------------------- |\n| ^2.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n| ^1.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n\n- (1) any version of `jest` should be greater or equal than 26.5.0 if you are using `commonjs`\n- (2) in order to use `esm` build, you may need to enable experimental features of node, see [here](https://github.com/dubzzz/fast-check/blob/main/packages/test-jest-bundle-esm/package.json)\n- (3) >=14.15.0 is the minimal requirements for `jest`, >=12.17.0 is the one for `@fast-check/jest`\n- (4) timeout defined on jest might not be properly applied to fast-check for node 18 (until 18.17.0) and node 19, see [#4004](https://github.com/dubzzz/fast-check/pull/4004)\n","packages/packaged/README.md":"# `@fast-check/packaged`\n\nUtility package removing any files that will not be part of the final bundle published to npm registry\n\n\n\n\n\n---\n\n## Why?\n\nWhen publishing packages to npm registry, it is quite easy to forget about some files. It also happens many times that we want somehow to check the packaged bundle in some of our tests but totally forget that some files have not been added to the bundle and so that the final user will actually never be able to run this code.\n\nThis package mostly try to prevent this issue. It can easily be used in monorepos to emulate the bundled package when used against other packages of the monorepo to make sure others do not depend on internals or non published stuff.\n\n## Easy to use\n\nRun the following command at the root of your package to drop any file that will not make it in the final bundle published to npm.\n\n```bash\n# With npm\nnpx -p @fast-check/packaged packaged\n# With pnpm\npnpm --package=@fast-check/packaged dlx packaged\n# With yarn\nyarn dlx -p @fast-check/packaged packaged\n```\n\nβ οΈ You may want to try with `--dry-run` flag first to give it a try.\n\nIt also comes with some extra flags:\n\n- `--dry-run`: do not drop any file or directory from the file system and only print what would have been removed\n- `--keep \n\n\n\n---\n\n## Why?\n\nIn JavaScript, \"prototype poisoning\" is one of the most common source for CVEs or zero days. It allows attackers to change the behaviour of some defaults like `Array.prototype.map`, `Map`, `Set`... so that they behave differently and can be leveraged for evil stuffs. This package can be used in addition to `fast-check` in order to detect poisoning that may occur during your property based tests.\n\n## Easy to use\n\nThe package comes with:\n\n- `assertNoPoisoning`: assert that the defaults known when first importing the package in your code have not been changed\n- `restoreGlobals`: restore the defaults so that any change that could have been detected by `assertNoPoisoning` will be resolved\n\n## Minimal requirements\n\n- Node β₯20.19.0\n","packages/vitest/README.md":"# `@fast-check/vitest`\n\n\n\nBring the power of property based testing framework `fast-check` into Vitest.\n`@fast-check/vitest` simplifies the integration of `fast-check` into Vitest.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/vitest`:\n\n```bash\nnpm install --save-dev @fast-check/vitest\n```\n\nIn order to work properly, `@fast-check/vitest` requires `vitest` to be installed.\n\n## Examples\n\nThe library comes with two modes, both powered by fast-check:\n\n- One-time random mode β A lightweight approach that introduces controlled randomness into your tests while keeping runs reproducible.\n- Property-based testing mode β A full-fledged property-based testing approach leveraging the full capabilities of fast-check.\n\n### One-time random mode\n\nThis mode extends Vitest's default `test` and `it` functions, allowing you to introduce controlled randomness into your tests while ensuring failures remain reproducible. This makes it easier to debug flaky tests and avoid irreproducible failures due to randomness.\n\nUnlike property-based testing, this mode does not run tests multiple times or attempt shrinking when failures occur. Instead, it provides a determistic way to introduce randomness when needed.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\nimport { expect } from 'vitest';\n\n// You can provide a fixed seed to force a replay by adding this line:\n// >> fc.configureGlobal({ seed })\n// Eventually you can disable shrinking capabilities with:\n// >> fc.configureGlobal({ endOnFailure: false })\n// >> // or combine it with the one above if you need both\n\ntest('test relying on randomness', ({ g }) => {\n // Arrange\n const user = {\n firstName: g(fc.string),\n lastName: g(fc.string),\n };\n\n // Act\n const displayName = computeDisplayName(user);\n\n // Assert\n expect(displayName).toContain(user.firstName);\n});\n\ntest('test not relying on randomness', () => {\n // your test\n});\n```\n\n### Full property-based mode\n\nFor more extensive testing, `@fast-check/vitest` also provides full support for property-based testing. This mode enables exhaustive, randomized testing by generating a variety of inputs and detecting edge cases automatically.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// same property but using named values\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nPlease note that the properties accepted by `@fast-check/vitest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances).\n\n### Seamless integration with Vitest's `beforeEach` / `afterEach`\n\nVitest's `beforeEach` and `afterEach` hooks are natively integrated into predicates. They are called respectively before and after each execution of the predicate. If a predicate runs _n_ times, `beforeEach` will be called _n_ times before it and `afterEach` _n_ times after it. The only caveat is that cleanup functions returned by `beforeEach` on the first predicate execution are deferred until the end of the test, as they are handled by vitest's own teardown mechanism. All other cleanups run between predicate executions as expected.\n\n### Advanced\n\nIf you want to forward custom parameters to fast-check, `test.prop` accepts an optional `fc.Parameters` ([more](https://github.com/dubzzz/fast-check/blob/main/documentation/1-Guides/Runners.md#runners)).\n\n`@fast-check/vitest` also comes with `.only`, `.skip`, `.todo` and `.concurrent` from vitest. It also accepts more complex ones such as `.concurrent.skip`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/vitest';\n\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n## Minimal requirements\n\n| @fast-check/vitest | vitest | fast-check | Node |\n| ------------------ | ------------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------- |\n| **0.4** | ^4.1.0 \\|\\| ^5.0.0 | ^3.0.0 \\|\\| ^4.0.0 | β₯20.19.0(2) (Vitest 4)\n\n\n\n---\n\n## Why?\n\n`fast-check` alone is great but what if it led your code into an infinite and synchronous loop for such inputs? In such case, it would neither be able to shrink the issue, nor to report any for you as the single threaded philosophy at the root of JavaScript will prevent it from anything except waiting for the main thread to come back.\n\nThis package tends to provide a way to run easily your properties within dedicated workers automatically spawed by it.\n\n## Example\n\nHere are some of the changes you will have to do:\n\n- hoist properties so that they get declared on the root scope\n- replace `fc.property` by `property` coming from `propertyFor(\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/ava`:\n\n```bash\nnpm install --save-dev @fast-check/ava\n```\n\nIn order to work properly, `@fast-check/ava` requires `ava` to be installed.\n\n## Example\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntestProp('should detect the substring', [fc.string(), fc.string(), fc.string()], (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n});\n```\n\nThe property is passed [AVA's `t` argument](https://github.com/avajs/ava/blob/main/docs/02-execution-context.md#execution-context-t-argument) as its first parameter, and the value of each arbitrary for the current test case for the rest of the parameters.\n\n`@fast-check/ava` supports all of [AVA's assertions](https://github.com/avajs/ava/blob/main/docs/03-assertions.md#assertions) and like AVA, it supports synchronous and asynchronous functions, including promises, observables, and callbacks. See [AVA's documentation](https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#declaring-test) for more information.\n\nβ οΈ **WARNING:** When relying on `@fast-check/ava`, returning `true` or `false` in your predicates is not taken into account. The library wants assertions or plans to be defined as `ava` itself does. Nonetheless you can still use primitives such as `fc.pre` to cut runs at the middle if some invariants are unmeet: the started plan (if any) will just be ignored.\n\n## Advanced\n\n### `fast-check` Parameters\n\n`testProp` accepts an optional `fc.Parameters` for forwarding custom parameters to `fast-check` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should detect the substring',\n [fc.string(), fc.string(), fc.string()],\n (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n },\n { numRuns: 10 }, // Example of parameters\n);\n```\n\n### AVA Modifiers\n\n`@fast-check/ava` also comes with [`.only`], [`.serial`] [`.skip`], and [`.failing`] modifiers from AVA.\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should replay the test for the seed 4242',\n [fc.nat(), fc.nat()],\n (t, a, b) => {\n t.is(a + b, b + a);\n },\n { seed: 4242 },\n);\n\ntestProp.skip('should be skipped', [fc.string()], (t, text) => {\n t.is([...text].length, text.length);\n});\n```\n\n[`.only`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-specific-tests\n[`.serial`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-tests-serially\n[`.skip`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#skipping-tests\n[`.failing`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#failing-tests\n\n### AVA `before`/`after` Hooks\n\n`@fast-check/ava` exposes AVA's `before`/`after` [hooks]:\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp.before((t) => {\n connectToDatabase();\n});\n\ntestProp();\n// ... omitted for brevity\n\ntestProp.after((t) => {\n closeDatabaseConnection();\n});\n```\n\n[hooks]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#before--after-hooks\n\n### AVA Execution Context\n\n`@fast-check/ava` mirror's AVA's procedure for customizing the test [execution context]:\n\n```typescript\nimport { fc, testProp as anyTestProp, PropertyTestInterface } from '@fast-check/ava';\n\ntype TestContext = {\n state: string;\n};\n\nconst testProp = anyTestProp as PropertyTestInterface\n\nProperty based testing framework for JavaScript/TypeScript\n
\n\n\n \n \n \n
\n \n \n \n
\n
\n \n \n
\n\nYou can also become one of them by contributing via [GitHub Sponsors](https://github.com/sponsors/dubzzz) or [OpenCollective](https://opencollective.com/fast-check/contribute).\n","isInternal":false,"tokens":13362,"sizeBytes":42944},{"name":"README.md","path":"packages/jest/README.md","rawUrl":"https://raw.githubusercontent.com/dubzzz/fast-check/HEAD/packages/jest/README.md","title":"jest Documentation","category":"plugin-manifest","format":"markdown","content":"# `@fast-check/jest`\n\n\n\nBring the power of property based testing framework `fast-check` into Jest.\n`@fast-check/jest` simplifies the integration of `fast-check` into Jest testing framework.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/jest`:\n\n```bash\nnpm install --save-dev @fast-check/jest\n```\n\nIn order to work properly, `@fast-check/jest` requires `jest` to be installed.\n\nWe also highly recommend users to launch their tests using the `--show-seed` option provided by Jest. It ensures Jest will always print the seed by itself (requires Jest β₯29.2.0).\n\n```sh\njest --show-seed\n```\n\n## Example\n\n```javascript\nimport { test, fc } from '@fast-check/jest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// Or the exact same test but based on named parameters\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nThe `it` and `test` functions returned by `@fast-check/jest` are just enriched versions of the ones coming from `jest` itself. They both come with `.prop`.\n\nPlease note that the properties accepted by `@fast-check/jest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances). In other words, the predicate passed as the last argument can be asynchronous.\n\n**Remark:** `it` and `test` have been introduced in 1.4.0. You have to refer to [Deprecated API](#deprecated-api) if you are using a version of `@fast-check/jest` <1.4.0.\n\n## Advanced\n\n### Support for variations of `test` and `it`\n\nIf you want to forward custom parameters to `fast-check`, `test.prop` and its variants accept an optional `fc.Parameters` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n`@fast-check/jest` also comes with support for `.only`, `.skip`, `.todo` and `.concurrent` from `jest`. It also accepts more complex ones such as `.concurrent.failing` or `.concurrent.only.failing`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/jest';\n\n// With custom `fc.Parameters`, here { seed: 4242 }\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\n// With .skip\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\n// With it version\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n### Experimental worker-based runner\n\n**The following feature is experimental!** When used it makes runners able to kill long running synchonous code. Meaning that it will make fast-check able to kill infinite loops blocking the main thread. So far, the feature does not fully support transformations performed via transform steps defined with jest.\n\nThe CommonJS approach would be:\n\n```js\nconst { init, fc } = require('@fast-check/jest/worker');\nconst { pathToFileURL } = require('node:url');\n\nconst { test, expect } = init(pathToFileURL(__filename));\n// can also be passed options such as isolationLevel: init(pathToFileURL(__filename), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nThe ES Modules approach would be:\n\n```js\nimport { init, fc } from '@fast-check/jest/worker';\n\nconst { test, expect } = await init(new URL(import.meta.url));\n// can also be passed options such as isolationLevel: init(new URL(import.meta.url), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nβ οΈ Do not forget to add the `await` before `init` for the ES Module version!\n\n#### Extra setup for `@fast-check/worker` 0.6.0 and later\n\nSince `@fast-check/worker` is an ESM-only package, running it under Jest in CommonJS mode requires `babel-jest` to transpile it. Install the following dependencies:\n\n```bash\nnpm install --save-dev babel-jest @babel/core @babel/preset-env\n```\n\nThen add a `babel.config.cjs` at the root of your project:\n\n```js\nmodule.exports = {\n presets: [['@babel/preset-env', { targets: { node: 'current' }, modules: 'commonjs' }]],\n};\n```\n\nAnd update your Jest configuration to use `babel-jest` while excluding `@fast-check/worker` from the ignore patterns:\n\n```js\nmodule.exports = {\n transform: {\n '^.+\\\\.[t|j]sx?$': 'babel-jest',\n },\n transformIgnorePatterns: ['/node_modules/(?!(?:@fast-check/worker)/)'],\n};\n```\n\nThis ensures `@fast-check/worker` gets transpiled to CommonJS by Babel instead of being skipped. Without it, Jest will fail to load the ESM-only package.\n\nFor ES Modules mode, no extra setup is needed β just make sure to run Jest with `--experimental-vm-modules`:\n\n```bash\nnode --experimental-vm-modules node_modules/jest/bin/jest.js\n```\n\n## Minimal requirements\n\n| @fast-check/jest | jest | fast-check | node |\n| ---------------- | --------------------------------------- | ---------- | ------------------------------------------------------------------------------------- |\n| ^2.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n| ^1.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n\n- (1) any version of `jest` should be greater or equal than 26.5.0 if you are using `commonjs`\n- (2) in order to use `esm` build, you may need to enable experimental features of node, see [here](https://github.com/dubzzz/fast-check/blob/main/packages/test-jest-bundle-esm/package.json)\n- (3) >=14.15.0 is the minimal requirements for `jest`, >=12.17.0 is the one for `@fast-check/jest`\n- (4) timeout defined on jest might not be properly applied to fast-check for node 18 (until 18.17.0) and node 19, see [#4004](https://github.com/dubzzz/fast-check/pull/4004)\n","isInternal":false,"tokens":1812,"sizeBytes":6639},{"name":"README.md","path":"packages/packaged/README.md","rawUrl":"https://raw.githubusercontent.com/dubzzz/fast-check/HEAD/packages/packaged/README.md","title":"packaged Documentation","category":"plugin-manifest","format":"markdown","content":"# `@fast-check/packaged`\n\nUtility package removing any files that will not be part of the final bundle published to npm registry\n\n\n\n\n\n---\n\n## Why?\n\nWhen publishing packages to npm registry, it is quite easy to forget about some files. It also happens many times that we want somehow to check the packaged bundle in some of our tests but totally forget that some files have not been added to the bundle and so that the final user will actually never be able to run this code.\n\nThis package mostly try to prevent this issue. It can easily be used in monorepos to emulate the bundled package when used against other packages of the monorepo to make sure others do not depend on internals or non published stuff.\n\n## Easy to use\n\nRun the following command at the root of your package to drop any file that will not make it in the final bundle published to npm.\n\n```bash\n# With npm\nnpx -p @fast-check/packaged packaged\n# With pnpm\npnpm --package=@fast-check/packaged dlx packaged\n# With yarn\nyarn dlx -p @fast-check/packaged packaged\n```\n\nβ οΈ You may want to try with `--dry-run` flag first to give it a try.\n\nIt also comes with some extra flags:\n\n- `--dry-run`: do not drop any file or directory from the file system and only print what would have been removed\n- `--keep \n\n\n\n---\n\n## Why?\n\nIn JavaScript, \"prototype poisoning\" is one of the most common source for CVEs or zero days. It allows attackers to change the behaviour of some defaults like `Array.prototype.map`, `Map`, `Set`... so that they behave differently and can be leveraged for evil stuffs. This package can be used in addition to `fast-check` in order to detect poisoning that may occur during your property based tests.\n\n## Easy to use\n\nThe package comes with:\n\n- `assertNoPoisoning`: assert that the defaults known when first importing the package in your code have not been changed\n- `restoreGlobals`: restore the defaults so that any change that could have been detected by `assertNoPoisoning` will be resolved\n\n## Minimal requirements\n\n- Node β₯20.19.0\n","isInternal":false,"tokens":347,"sizeBytes":1378},{"name":"README.md","path":"packages/vitest/README.md","rawUrl":"https://raw.githubusercontent.com/dubzzz/fast-check/HEAD/packages/vitest/README.md","title":"vitest Documentation","category":"plugin-manifest","format":"markdown","content":"# `@fast-check/vitest`\n\n\n\nBring the power of property based testing framework `fast-check` into Vitest.\n`@fast-check/vitest` simplifies the integration of `fast-check` into Vitest.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/vitest`:\n\n```bash\nnpm install --save-dev @fast-check/vitest\n```\n\nIn order to work properly, `@fast-check/vitest` requires `vitest` to be installed.\n\n## Examples\n\nThe library comes with two modes, both powered by fast-check:\n\n- One-time random mode β A lightweight approach that introduces controlled randomness into your tests while keeping runs reproducible.\n- Property-based testing mode β A full-fledged property-based testing approach leveraging the full capabilities of fast-check.\n\n### One-time random mode\n\nThis mode extends Vitest's default `test` and `it` functions, allowing you to introduce controlled randomness into your tests while ensuring failures remain reproducible. This makes it easier to debug flaky tests and avoid irreproducible failures due to randomness.\n\nUnlike property-based testing, this mode does not run tests multiple times or attempt shrinking when failures occur. Instead, it provides a determistic way to introduce randomness when needed.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\nimport { expect } from 'vitest';\n\n// You can provide a fixed seed to force a replay by adding this line:\n// >> fc.configureGlobal({ seed })\n// Eventually you can disable shrinking capabilities with:\n// >> fc.configureGlobal({ endOnFailure: false })\n// >> // or combine it with the one above if you need both\n\ntest('test relying on randomness', ({ g }) => {\n // Arrange\n const user = {\n firstName: g(fc.string),\n lastName: g(fc.string),\n };\n\n // Act\n const displayName = computeDisplayName(user);\n\n // Assert\n expect(displayName).toContain(user.firstName);\n});\n\ntest('test not relying on randomness', () => {\n // your test\n});\n```\n\n### Full property-based mode\n\nFor more extensive testing, `@fast-check/vitest` also provides full support for property-based testing. This mode enables exhaustive, randomized testing by generating a variety of inputs and detecting edge cases automatically.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// same property but using named values\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nPlease note that the properties accepted by `@fast-check/vitest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances).\n\n### Seamless integration with Vitest's `beforeEach` / `afterEach`\n\nVitest's `beforeEach` and `afterEach` hooks are natively integrated into predicates. They are called respectively before and after each execution of the predicate. If a predicate runs _n_ times, `beforeEach` will be called _n_ times before it and `afterEach` _n_ times after it. The only caveat is that cleanup functions returned by `beforeEach` on the first predicate execution are deferred until the end of the test, as they are handled by vitest's own teardown mechanism. All other cleanups run between predicate executions as expected.\n\n### Advanced\n\nIf you want to forward custom parameters to fast-check, `test.prop` accepts an optional `fc.Parameters` ([more](https://github.com/dubzzz/fast-check/blob/main/documentation/1-Guides/Runners.md#runners)).\n\n`@fast-check/vitest` also comes with `.only`, `.skip`, `.todo` and `.concurrent` from vitest. It also accepts more complex ones such as `.concurrent.skip`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/vitest';\n\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n## Minimal requirements\n\n| @fast-check/vitest | vitest | fast-check | Node |\n| ------------------ | ------------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------- |\n| **0.4** | ^4.1.0 \\|\\| ^5.0.0 | ^3.0.0 \\|\\| ^4.0.0 | β₯20.19.0(2) (Vitest 4)\n\n\n\n---\n\n## Why?\n\n`fast-check` alone is great but what if it led your code into an infinite and synchronous loop for such inputs? In such case, it would neither be able to shrink the issue, nor to report any for you as the single threaded philosophy at the root of JavaScript will prevent it from anything except waiting for the main thread to come back.\n\nThis package tends to provide a way to run easily your properties within dedicated workers automatically spawed by it.\n\n## Example\n\nHere are some of the changes you will have to do:\n\n- hoist properties so that they get declared on the root scope\n- replace `fc.property` by `property` coming from `propertyFor(\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/ava`:\n\n```bash\nnpm install --save-dev @fast-check/ava\n```\n\nIn order to work properly, `@fast-check/ava` requires `ava` to be installed.\n\n## Example\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntestProp('should detect the substring', [fc.string(), fc.string(), fc.string()], (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n});\n```\n\nThe property is passed [AVA's `t` argument](https://github.com/avajs/ava/blob/main/docs/02-execution-context.md#execution-context-t-argument) as its first parameter, and the value of each arbitrary for the current test case for the rest of the parameters.\n\n`@fast-check/ava` supports all of [AVA's assertions](https://github.com/avajs/ava/blob/main/docs/03-assertions.md#assertions) and like AVA, it supports synchronous and asynchronous functions, including promises, observables, and callbacks. See [AVA's documentation](https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#declaring-test) for more information.\n\nβ οΈ **WARNING:** When relying on `@fast-check/ava`, returning `true` or `false` in your predicates is not taken into account. The library wants assertions or plans to be defined as `ava` itself does. Nonetheless you can still use primitives such as `fc.pre` to cut runs at the middle if some invariants are unmeet: the started plan (if any) will just be ignored.\n\n## Advanced\n\n### `fast-check` Parameters\n\n`testProp` accepts an optional `fc.Parameters` for forwarding custom parameters to `fast-check` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should detect the substring',\n [fc.string(), fc.string(), fc.string()],\n (t, a, b, c) => {\n t.true((a + b + c).includes(b));\n },\n { numRuns: 10 }, // Example of parameters\n);\n```\n\n### AVA Modifiers\n\n`@fast-check/ava` also comes with [`.only`], [`.serial`] [`.skip`], and [`.failing`] modifiers from AVA.\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp(\n 'should replay the test for the seed 4242',\n [fc.nat(), fc.nat()],\n (t, a, b) => {\n t.is(a + b, b + a);\n },\n { seed: 4242 },\n);\n\ntestProp.skip('should be skipped', [fc.string()], (t, text) => {\n t.is([...text].length, text.length);\n});\n```\n\n[`.only`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-specific-tests\n[`.serial`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#running-tests-serially\n[`.skip`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#skipping-tests\n[`.failing`]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#failing-tests\n\n### AVA `before`/`after` Hooks\n\n`@fast-check/ava` exposes AVA's `before`/`after` [hooks]:\n\n```typescript\nimport { testProp, fc } from '@fast-check/ava';\n\ntestProp.before((t) => {\n connectToDatabase();\n});\n\ntestProp();\n// ... omitted for brevity\n\ntestProp.after((t) => {\n closeDatabaseConnection();\n});\n```\n\n[hooks]: https://github.com/avajs/ava/blob/main/docs/01-writing-tests.md#before--after-hooks\n\n### AVA Execution Context\n\n`@fast-check/ava` mirror's AVA's procedure for customizing the test [execution context]:\n\n```typescript\nimport { fc, testProp as anyTestProp, PropertyTestInterface } from '@fast-check/ava';\n\ntype TestContext = {\n state: string;\n};\n\nconst testProp = anyTestProp as PropertyTestInterface\n\nProperty based testing framework for JavaScript/TypeScript\n
\n\n\n \n \n \n
\n \n \n \n
\n
\n \n \n
\n\nYou can also become one of them by contributing via [GitHub Sponsors](https://github.com/sponsors/dubzzz) or [OpenCollective](https://opencollective.com/fast-check/contribute).\n\n\n# `@fast-check/jest`\n\n\n\nBring the power of property based testing framework `fast-check` into Jest.\n`@fast-check/jest` simplifies the integration of `fast-check` into Jest testing framework.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/jest`:\n\n```bash\nnpm install --save-dev @fast-check/jest\n```\n\nIn order to work properly, `@fast-check/jest` requires `jest` to be installed.\n\nWe also highly recommend users to launch their tests using the `--show-seed` option provided by Jest. It ensures Jest will always print the seed by itself (requires Jest β₯29.2.0).\n\n```sh\njest --show-seed\n```\n\n## Example\n\n```javascript\nimport { test, fc } from '@fast-check/jest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// Or the exact same test but based on named parameters\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nThe `it` and `test` functions returned by `@fast-check/jest` are just enriched versions of the ones coming from `jest` itself. They both come with `.prop`.\n\nPlease note that the properties accepted by `@fast-check/jest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances). In other words, the predicate passed as the last argument can be asynchronous.\n\n**Remark:** `it` and `test` have been introduced in 1.4.0. You have to refer to [Deprecated API](#deprecated-api) if you are using a version of `@fast-check/jest` <1.4.0.\n\n## Advanced\n\n### Support for variations of `test` and `it`\n\nIf you want to forward custom parameters to `fast-check`, `test.prop` and its variants accept an optional `fc.Parameters` ([more](https://fast-check.dev/docs/core-blocks/runners/#assert)).\n\n`@fast-check/jest` also comes with support for `.only`, `.skip`, `.todo` and `.concurrent` from `jest`. It also accepts more complex ones such as `.concurrent.failing` or `.concurrent.only.failing`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/jest';\n\n// With custom `fc.Parameters`, here { seed: 4242 }\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\n// With .skip\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\n// With it version\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n### Experimental worker-based runner\n\n**The following feature is experimental!** When used it makes runners able to kill long running synchonous code. Meaning that it will make fast-check able to kill infinite loops blocking the main thread. So far, the feature does not fully support transformations performed via transform steps defined with jest.\n\nThe CommonJS approach would be:\n\n```js\nconst { init, fc } = require('@fast-check/jest/worker');\nconst { pathToFileURL } = require('node:url');\n\nconst { test, expect } = init(pathToFileURL(__filename));\n// can also be passed options such as isolationLevel: init(pathToFileURL(__filename), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nThe ES Modules approach would be:\n\n```js\nimport { init, fc } from '@fast-check/jest/worker';\n\nconst { test, expect } = await init(new URL(import.meta.url));\n// can also be passed options such as isolationLevel: init(new URL(import.meta.url), {})\n\ntest.prop([fc.constant(null)])('should pass', (value) => {\n expect(value).toBe(null);\n});\n```\n\nβ οΈ Do not forget to add the `await` before `init` for the ES Module version!\n\n#### Extra setup for `@fast-check/worker` 0.6.0 and later\n\nSince `@fast-check/worker` is an ESM-only package, running it under Jest in CommonJS mode requires `babel-jest` to transpile it. Install the following dependencies:\n\n```bash\nnpm install --save-dev babel-jest @babel/core @babel/preset-env\n```\n\nThen add a `babel.config.cjs` at the root of your project:\n\n```js\nmodule.exports = {\n presets: [['@babel/preset-env', { targets: { node: 'current' }, modules: 'commonjs' }]],\n};\n```\n\nAnd update your Jest configuration to use `babel-jest` while excluding `@fast-check/worker` from the ignore patterns:\n\n```js\nmodule.exports = {\n transform: {\n '^.+\\\\.[t|j]sx?$': 'babel-jest',\n },\n transformIgnorePatterns: ['/node_modules/(?!(?:@fast-check/worker)/)'],\n};\n```\n\nThis ensures `@fast-check/worker` gets transpiled to CommonJS by Babel instead of being skipped. Without it, Jest will fail to load the ESM-only package.\n\nFor ES Modules mode, no extra setup is needed β just make sure to run Jest with `--experimental-vm-modules`:\n\n```bash\nnode --experimental-vm-modules node_modules/jest/bin/jest.js\n```\n\n## Minimal requirements\n\n| @fast-check/jest | jest | fast-check | node |\n| ---------------- | --------------------------------------- | ---------- | ------------------------------------------------------------------------------------- |\n| ^2.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n| ^1.0.0 | >=26.5.0(1)(2) | ^3.0.0 | >=14.15.0(3) and <18, >=18.17.0 and <19(4), >=20 |\n\n- (1) any version of `jest` should be greater or equal than 26.5.0 if you are using `commonjs`\n- (2) in order to use `esm` build, you may need to enable experimental features of node, see [here](https://github.com/dubzzz/fast-check/blob/main/packages/test-jest-bundle-esm/package.json)\n- (3) >=14.15.0 is the minimal requirements for `jest`, >=12.17.0 is the one for `@fast-check/jest`\n- (4) timeout defined on jest might not be properly applied to fast-check for node 18 (until 18.17.0) and node 19, see [#4004](https://github.com/dubzzz/fast-check/pull/4004)\n\n\n# `@fast-check/packaged`\n\nUtility package removing any files that will not be part of the final bundle published to npm registry\n\n\n\n\n\n---\n\n## Why?\n\nWhen publishing packages to npm registry, it is quite easy to forget about some files. It also happens many times that we want somehow to check the packaged bundle in some of our tests but totally forget that some files have not been added to the bundle and so that the final user will actually never be able to run this code.\n\nThis package mostly try to prevent this issue. It can easily be used in monorepos to emulate the bundled package when used against other packages of the monorepo to make sure others do not depend on internals or non published stuff.\n\n## Easy to use\n\nRun the following command at the root of your package to drop any file that will not make it in the final bundle published to npm.\n\n```bash\n# With npm\nnpx -p @fast-check/packaged packaged\n# With pnpm\npnpm --package=@fast-check/packaged dlx packaged\n# With yarn\nyarn dlx -p @fast-check/packaged packaged\n```\n\nβ οΈ You may want to try with `--dry-run` flag first to give it a try.\n\nIt also comes with some extra flags:\n\n- `--dry-run`: do not drop any file or directory from the file system and only print what would have been removed\n- `--keep \n\n\n\n---\n\n## Why?\n\nIn JavaScript, \"prototype poisoning\" is one of the most common source for CVEs or zero days. It allows attackers to change the behaviour of some defaults like `Array.prototype.map`, `Map`, `Set`... so that they behave differently and can be leveraged for evil stuffs. This package can be used in addition to `fast-check` in order to detect poisoning that may occur during your property based tests.\n\n## Easy to use\n\nThe package comes with:\n\n- `assertNoPoisoning`: assert that the defaults known when first importing the package in your code have not been changed\n- `restoreGlobals`: restore the defaults so that any change that could have been detected by `assertNoPoisoning` will be resolved\n\n## Minimal requirements\n\n- Node β₯20.19.0\n\n\n# `@fast-check/vitest`\n\n\n\nBring the power of property based testing framework `fast-check` into Vitest.\n`@fast-check/vitest` simplifies the integration of `fast-check` into Vitest.\n\n\n\n\n\n---\n\n## Getting Started\n\nInstall `@fast-check/vitest`:\n\n```bash\nnpm install --save-dev @fast-check/vitest\n```\n\nIn order to work properly, `@fast-check/vitest` requires `vitest` to be installed.\n\n## Examples\n\nThe library comes with two modes, both powered by fast-check:\n\n- One-time random mode β A lightweight approach that introduces controlled randomness into your tests while keeping runs reproducible.\n- Property-based testing mode β A full-fledged property-based testing approach leveraging the full capabilities of fast-check.\n\n### One-time random mode\n\nThis mode extends Vitest's default `test` and `it` functions, allowing you to introduce controlled randomness into your tests while ensuring failures remain reproducible. This makes it easier to debug flaky tests and avoid irreproducible failures due to randomness.\n\nUnlike property-based testing, this mode does not run tests multiple times or attempt shrinking when failures occur. Instead, it provides a determistic way to introduce randomness when needed.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\nimport { expect } from 'vitest';\n\n// You can provide a fixed seed to force a replay by adding this line:\n// >> fc.configureGlobal({ seed })\n// Eventually you can disable shrinking capabilities with:\n// >> fc.configureGlobal({ endOnFailure: false })\n// >> // or combine it with the one above if you need both\n\ntest('test relying on randomness', ({ g }) => {\n // Arrange\n const user = {\n firstName: g(fc.string),\n lastName: g(fc.string),\n };\n\n // Act\n const displayName = computeDisplayName(user);\n\n // Assert\n expect(displayName).toContain(user.firstName);\n});\n\ntest('test not relying on randomness', () => {\n // your test\n});\n```\n\n### Full property-based mode\n\nFor more extensive testing, `@fast-check/vitest` also provides full support for property-based testing. This mode enables exhaustive, randomized testing by generating a variety of inputs and detecting edge cases automatically.\n\n```javascript\nimport { test, fc } from '@fast-check/vitest';\n\n// for all a, b, c strings\n// b is a substring of a + b + c\ntest.prop([fc.string(), fc.string(), fc.string()])('should detect the substring', (a, b, c) => {\n return (a + b + c).includes(b);\n});\n\n// same property but using named values\ntest.prop({ a: fc.string(), b: fc.string(), c: fc.string() })('should detect the substring', ({ a, b, c }) => {\n return (a + b + c).includes(b);\n});\n```\n\nPlease note that the properties accepted by `@fast-check/vitest` as input can either be synchronous or asynchronous (even just `PromiseLike` instances).\n\n### Seamless integration with Vitest's `beforeEach` / `afterEach`\n\nVitest's `beforeEach` and `afterEach` hooks are natively integrated into predicates. They are called respectively before and after each execution of the predicate. If a predicate runs _n_ times, `beforeEach` will be called _n_ times before it and `afterEach` _n_ times after it. The only caveat is that cleanup functions returned by `beforeEach` on the first predicate execution are deferred until the end of the test, as they are handled by vitest's own teardown mechanism. All other cleanups run between predicate executions as expected.\n\n### Advanced\n\nIf you want to forward custom parameters to fast-check, `test.prop` accepts an optional `fc.Parameters` ([more](https://github.com/dubzzz/fast-check/blob/main/documentation/1-Guides/Runners.md#runners)).\n\n`@fast-check/vitest` also comes with `.only`, `.skip`, `.todo` and `.concurrent` from vitest. It also accepts more complex ones such as `.concurrent.skip`.\n\n```javascript\nimport { it, test, fc } from '@fast-check/vitest';\n\ntest.prop([fc.nat(), fc.nat()], { seed: 4242 })('should replay the test for the seed 4242', (a, b) => {\n return a + b === b + a;\n});\n\ntest.skip.prop([fc.string()])('should be skipped', (text) => {\n return text.length === [...text].length;\n});\n\ndescribe('with it', () => {\n it.prop([fc.nat(), fc.nat()])('should run too', (a, b) => {\n return a + b === b + a;\n });\n});\n```\n\n## Minimal requirements\n\n| @fast-check/vitest | vitest | fast-check | Node |\n| ------------------ | ------------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------- |\n| **0.4** | ^4.1.0 \\|\\| ^5.0.0 | ^3.0.0 \\|\\| ^4.0.0 | β₯20.19.0(2) (Vitest 4)\n\n\n\n---\n\n## Why?\n\n`fast-check` alone is great but what if it led your code into an infinite and synchronous loop for such inputs? In such case, it would neither be able to shrink the issue, nor to report any for you as the single threaded philosophy at the root of JavaScript will prevent it from anything except waiting for the main thread to come back.\n\nThis package tends to provide a way to run easily your properties within dedicated workers automatically spawed by it.\n\n## Example\n\nHere are some of the changes you will have to do:\n\n- hoist properties so that they get declared on the root scope\n- replace `fc.property` by `property` coming from `propertyFor(![\"Nicolas](\"https://avatars.githubusercontent.com/u/5300235?v=4?s=100\")
![\"Aaron](\"https://avatars.githubusercontent.com/u/381037?v=4?s=100\")
![\"Will](\"https://avatars.githubusercontent.com/u/5377213?v=4?s=100\")
![\"kazchimo\"/](\"https://avatars.githubusercontent.com/u/31263328?v=4?s=100\")
![\"Brandon](\"https://avatars.githubusercontent.com/u/27799541?v=4?s=100\")
![\"Irakli](\"https://avatars.githubusercontent.com/u/1932383?v=4?s=100\")
![\"Andrew](\"https://avatars.githubusercontent.com/u/298292?v=4?s=100\")
![\"Eric](\"https://avatars.githubusercontent.com/u/1596818?v=4?s=100\")
![\"burrscurr\"/](\"https://avatars.githubusercontent.com/u/23213508?v=4?s=100\")
![\"JC](\"https://avatars.githubusercontent.com/u/11434205?v=4?s=100\")
![\"Larry](\"https://avatars.githubusercontent.com/u/1510520?v=4?s=100\")
![\"Roman](\"https://avatars.githubusercontent.com/u/5839225?v=4?s=100\")
![\"Tim](\"https://avatars.githubusercontent.com/u/761444?v=4?s=100\")
![\"Brais](\"https://avatars.githubusercontent.com/u/17855450?v=4?s=100\")
![\"Renaud-Pierre](\"https://avatars.githubusercontent.com/u/118620?v=4?s=100\")
![\"Jemma](\"https://avatars.githubusercontent.com/u/190414?v=4?s=100\")
![\"John](\"https://avatars.githubusercontent.com/u/77482?v=4?s=100\")
![\"Trey](\"https://avatars.githubusercontent.com/u/1691239?v=4?s=100\")
![\"Leon](\"https://avatars.githubusercontent.com/u/36966635?v=4?s=100\")
![\"Gorgi](\"https://avatars.githubusercontent.com/u/502412?v=4?s=100\")
![\"mayconsacht\"/](\"https://avatars.githubusercontent.com/u/5214042?v=4?s=100\")
![\"Simon](\"https://avatars.githubusercontent.com/u/521604?v=4?s=100\")
![\"Richard](\"https://avatars.githubusercontent.com/u/1199584?v=4?s=100\")
![\"Alan](\"https://avatars.githubusercontent.com/u/475?v=4?s=100\")
![\"Makien](\"https://avatars.githubusercontent.com/u/90332566?v=4?s=100\")
![\"David](\"https://avatars.githubusercontent.com/u/7817485?v=4?s=100\")
![\"Diego](\"https://avatars.githubusercontent.com/u/7157796?v=4?s=100\")
![\"Borui](\"https://avatars.githubusercontent.com/u/8686167?v=4?s=100\")
![\"Brian](\"https://avatars.githubusercontent.com/u/1938?v=4?s=100\")
![\"volrk\"/](\"https://avatars.githubusercontent.com/u/32265974?v=4?s=100\")
![\"tinydylan\"/](\"https://avatars.githubusercontent.com/u/41112113?v=4?s=100\")
![\"Caleb](\"https://avatars.githubusercontent.com/u/10626596?v=4?s=100\")
![\"Rulai](\"https://avatars.githubusercontent.com/u/2570932?v=4?s=100\")
![\"Afonso](\"https://avatars.githubusercontent.com/u/19473034?v=4?s=100\")
![\"Tom](\"https://avatars.githubusercontent.com/u/3259993?v=4?s=100\")
![\"phormio\"/](\"https://avatars.githubusercontent.com/u/28146332?v=4?s=100\")
![\"Giovanni](\"https://avatars.githubusercontent.com/u/2643520?v=4?s=100\")
![\"Tomas](\"https://avatars.githubusercontent.com/u/34538?v=4?s=100\")
![\"Kirill](\"https://avatars.githubusercontent.com/u/7964583?v=4?s=100\")
![\"Giovanny](\"https://avatars.githubusercontent.com/u/5326411?v=4?s=100\")
![\"Mark](\"https://avatars.githubusercontent.com/u/34955942?v=4?s=100\")
![\"Peter](\"https://avatars.githubusercontent.com/u/354848?v=4?s=100\")
![\"Chinedu](\"https://avatars.githubusercontent.com/u/11678369?v=4?s=100\")
![\"Gunar](\"https://avatars.githubusercontent.com/u/7684574?v=4?s=100\")
![\"Christian](\"https://avatars.githubusercontent.com/u/18668440?v=4?s=100\")
![\"Tomer](\"https://avatars.githubusercontent.com/u/23299544?v=4?s=100\")
![\"0xflotus\"/](\"https://avatars.githubusercontent.com/u/26602940?v=4?s=100\")
![\"Ryan](\"https://avatars.githubusercontent.com/u/9272847?v=4?s=100\")
![\"Jason](\"https://avatars.githubusercontent.com/u/904007?v=4?s=100\")
![\"Matin](\"https://avatars.githubusercontent.com/u/24797481?v=4?s=100\")
![\"Juan](\"https://avatars.githubusercontent.com/u/500?v=4?s=100\")
![\"Simen](\"https://avatars.githubusercontent.com/u/1404810?v=4?s=100\")
![\"Tarjei](\"https://avatars.githubusercontent.com/u/25415972?v=4?s=100\")
![\"Denis](\"https://avatars.githubusercontent.com/u/829578?v=4?s=100\")
![\"Trevor](\"https://avatars.githubusercontent.com/u/3536716?v=4?s=100\")
![\"Grant](\"https://avatars.githubusercontent.com/u/1948935?v=4?s=100\")
![\"Attila](\"https://avatars.githubusercontent.com/u/5737996?v=4?s=100\")
![\"Zach](\"https://avatars.githubusercontent.com/u/469365?v=4?s=100\")
![\"Bennett](\"https://avatars.githubusercontent.com/u/1610227?v=4?s=100\")
![\"Alexandre](\"https://avatars.githubusercontent.com/u/4980521?v=4?s=100\")
![\"ej](\"https://avatars.githubusercontent.com/u/116496520?v=4?s=100\")
![\"Niklas](\"https://avatars.githubusercontent.com/u/26570572?v=4?s=100\")
![\"Patrick](\"https://avatars.githubusercontent.com/u/42661?v=4?s=100\")
![\"Cindy](\"https://avatars.githubusercontent.com/u/1177031?v=4?s=100\")
![\"Noah\"/](\"https://avatars.githubusercontent.com/u/35386821?v=4?s=100\")
![\"James](\"https://avatars.githubusercontent.com/u/2906913?v=4?s=100\")
![\"Alex](\"https://avatars.githubusercontent.com/u/109672176?v=4?s=100\")
![\"andrew](\"https://avatars.githubusercontent.com/u/15133992?v=4?s=100\")
![\"Matthias](\"https://avatars.githubusercontent.com/u/53833818?v=4?s=100\")
![\"Dolan](\"https://avatars.githubusercontent.com/u/1649120?v=4?s=100\")
![\"Emi\"/](\"https://avatars.githubusercontent.com/u/991554?v=4?s=100\")
![\"Russ](\"https://avatars.githubusercontent.com/u/8487728?v=4?s=100\")
![\"adamni21\"/](\"https://avatars.githubusercontent.com/u/85580454?v=4?s=100\")
![\"Joseph](\"https://avatars.githubusercontent.com/u/1519098?v=4?s=100\")
![\"Aleksey](\"https://avatars.githubusercontent.com/u/41122157?v=4?s=100\")
![\"rugk\"/](\"https://avatars.githubusercontent.com/u/11966684?v=4?s=100\")
![\"Jonathan](\"https://avatars.githubusercontent.com/u/25589715?v=4?s=100\")
![\"Alberto](\"https://avatars.githubusercontent.com/u/12381818?v=4?s=100\")
![\"Zek\"/](\"https://avatars.githubusercontent.com/u/3463291?v=4?s=100\")