feat(vanilla): add testing infrastructure and tests (NK-wjnczv)

1 files changed, 38 insertions, 0 deletions

diff --git a/vanilla/node_modules/vitest/dist/chunks/plugin.d.CtqpEehP.d.ts b/vanilla/node_modules/vitest/dist/chunks/plugin.d.CtqpEehP.d.ts
new file mode 100644
index 0000000..4955bd8
--- /dev/null
+++ b/vanilla/node_modules/vitest/dist/chunks/plugin.d.CtqpEehP.d.ts
@@ -0,0 +1,38 @@
+import { DevEnvironment } from 'vite';
+import { V as Vitest, T as TestProject, b as TestProjectConfiguration } from './reporters.d.CWXNI2jG.js';
+
+/**
+* Generate a unique cache identifier.
+*
+* Return `false` to disable caching of the file.
+* @experimental
+*/
+interface CacheKeyIdGenerator {
+	(context: CacheKeyIdGeneratorContext): string | undefined | null | false;
+}
+/**
+* @experimental
+*/
+interface CacheKeyIdGeneratorContext {
+	environment: DevEnvironment;
+	id: string;
+	sourceCode: string;
+}
+
+interface VitestPluginContext {
+	vitest: Vitest;
+	project: TestProject;
+	injectTestProjects: (config: TestProjectConfiguration | TestProjectConfiguration[]) => Promise<TestProject[]>;
+	/**
+	* Define a generator that will be applied before hashing the cache key.
+	*
+	* Use this to make sure Vitest generates correct hash. It is a good idea
+	* to define this function if your plugin can be registered with different options.
+	*
+	* This is called only if `experimental.fsModuleCache` is defined.
+	* @experimental
+	*/
+	experimental_defineCacheKeyGenerator: (callback: CacheKeyIdGenerator) => void;
+}
+
+export type { CacheKeyIdGenerator as C, VitestPluginContext as V, CacheKeyIdGeneratorContext as a };